diff options
| author | Eric W. Biederman <[email protected]> | 2006-10-21 18:37:02 +0200 |
|---|---|---|
| committer | Andi Kleen <[email protected]> | 2006-10-21 18:37:02 +0200 |
| commit | 6bf2dafad18c119beb534cbb3d882fe7a6c3f529 (patch) | |
| tree | c78450df76c5c624788aaf81154f1f2070bcd5a7 /fs/jbd/commit.c | |
| parent | a1bae67243512ca30ceda48e3e24e25b543f8ab7 (diff) | |
[PATCH] x86-64: Use irq_domain in ioapic_retrigger_irq
Thanks to YH Lu for spotting this. It appears I missed this function when I
refactored allocate_irq_vector and introduced irq_domain, with the result that
all retriggered irqs would go to cpu 0 even if we were not prepared to receive
them there.
While reviewing YH's patch I also noticed that this function was missing
locking, and since I am now reading two values from two diffrent arrays that
looks like a race we might be able to hit in the real world.
Cc: Yinghai Lu <[email protected]>
Signed-off-by: Eric W. Biederman <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Signed-off-by: Andi Kleen <[email protected]>
Diffstat (limited to 'fs/jbd/commit.c')
0 files changed, 0 insertions, 0 deletions