diff options
author | Matthew Wilcox <matthew@wil.cx> | 2008-11-20 16:09:33 -0500 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2008-11-20 16:17:40 -0500 |
commit | 0ca4b6b00113b064c080d26d803d0d7c80fb5dc8 (patch) | |
tree | 69e25f61bf252f2db0c0d01244555f90ad48aaf1 /arch/um | |
parent | 23918b03060f6e572168fdde1798a905679d2e06 (diff) |
x86: Fix interrupt leak due to migration
When we migrate an interrupt from one CPU to another, we set the
move_in_progress flag and clean up the vectors later once they're not
being used. If you're unlucky and call destroy_irq() before the vectors
become un-used, the move_in_progress flag is never cleared, which causes
the interrupt to become unusable.
This was discovered by Jesse Brandeburg for whom it manifested as an
MSI-X device refusing to use MSI-X mode when the driver was unloaded
and reloaded repeatedly.
Signed-off-by: Matthew Wilcox <willy@linux.intel.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'arch/um')
0 files changed, 0 insertions, 0 deletions