diff options
| author | NeilBrown <neilb@suse.de> | 2006-05-30 21:27:13 -0700 |
|---|---|---|
| committer | Linus Torvalds <torvalds@g5.osdl.org> | 2006-05-31 16:27:11 -0700 |
| commit | c331eb04b995ad276a7ece4608326f1db4e137d8 (patch) | |
| tree | d3ef167648eb00266696039cc10b32592747e5fe /include | |
| parent | a835fa798ddfbfe4c63ff5e22c93fa5d24c95f7b (diff) | |
| download | kernel_samsung_aries-c331eb04b995ad276a7ece4608326f1db4e137d8.zip kernel_samsung_aries-c331eb04b995ad276a7ece4608326f1db4e137d8.tar.gz kernel_samsung_aries-c331eb04b995ad276a7ece4608326f1db4e137d8.tar.bz2 | |
[PATCH] md: Fix badness in sysfs_notify caused by md_new_event
From: NeilBrown <neilb@suse.de>
If an error is reported by a drive in a RAID array (which is done via
bi_end_io - in interrupt context), we call md_error and md_new_event which
calls sysfs_notify. However sysfs_notify grabs a mutex and so cannot be
called in interrupt context.
This patch just creates a variant of md_new_event which avoids the sysfs
call, and uses that. A better fix for later is to arrange for the event to
be called from user-context.
Note: avoiding the sysfs call isn't a problem as an error will not, by
itself, modify the sync_action attribute. (We do still need to
wake_up(&md_event_waiters) as an error by itself will modify /proc/mdstat).
Signed-off-by: Neil Brown <neilb@suse.de>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions