diff options
| author | Heiner Kallweit <hkallweit1@gmail.com> | 2020-10-29 10:18:53 +0100 |
|---|---|---|
| committer | Jakub Kicinski <kuba@kernel.org> | 2020-10-29 11:49:04 -0700 |
| commit | 2734a24e6e5d18522fbf599135c59b82ec9b2c9e (patch) | |
| tree | 4242cb57462ed4b69b8a90e336b3063a9e5fc7fc /net | |
| parent | eadd1befdd778a1eca57fad058782bd22b4db804 (diff) | |
| download | linux-2734a24e6e5d18522fbf599135c59b82ec9b2c9e.tar.gz linux-2734a24e6e5d18522fbf599135c59b82ec9b2c9e.tar.bz2 linux-2734a24e6e5d18522fbf599135c59b82ec9b2c9e.zip | |
r8169: fix issue with forced threading in combination with shared interrupts
As reported by Serge flag IRQF_NO_THREAD causes an error if the
interrupt is actually shared and the other driver(s) don't have this
flag set. This situation can occur if a PCI(e) legacy interrupt is
used in combination with forced threading.
There's no good way to deal with this properly, therefore we have to
remove flag IRQF_NO_THREAD. For fixing the original forced threading
issue switch to napi_schedule().
Fixes: 424a646e072a ("r8169: fix operation under forced interrupt threading")
Link: https://www.spinics.net/lists/netdev/msg694960.html
Reported-by: Serge Belyshev <belyshev@depni.sinp.msu.ru>
Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
Tested-by: Serge Belyshev <belyshev@depni.sinp.msu.ru>
Link: https://lore.kernel.org/r/b5b53bfe-35ac-3768-85bf-74d1290cf394@gmail.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions