diff options
| author | James Bottomley <James.Bottomley@SteelEye.com> | 2005-08-26 18:34:17 -0700 |
|---|---|---|
| committer | Linus Torvalds <torvalds@g5.osdl.org> | 2005-08-26 19:37:13 -0700 |
| commit | 36676bcbf9f6bcbea9d06e67ee8d04eacde54952 (patch) | |
| tree | f31e9a79a643cfba649637164a559d94b4183ccc /arch | |
| parent | 657390d25d4241705cb4fc5b3b4ba5b30575dc17 (diff) | |
| download | kernel_samsung_smdk4412-36676bcbf9f6bcbea9d06e67ee8d04eacde54952.zip kernel_samsung_smdk4412-36676bcbf9f6bcbea9d06e67ee8d04eacde54952.tar.gz kernel_samsung_smdk4412-36676bcbf9f6bcbea9d06e67ee8d04eacde54952.tar.bz2 | |
[PATCH] Fix oops in sysfs_hash_and_remove_file()
The problem arises if an entity in sysfs is created and removed without
ever having been made completely visible. In SCSI this is triggered by
removing a device while it's initialising.
The problem appears to be that because it was never made visible in sysfs,
the sysfs dentry has a null d_inode which oopses when a reference is made
to it. The solution is simply to check d_inode and assume the object was
never made visible (and thus doesn't need deleting) if it's NULL.
(akpm: possibly a stopgap for 2.6.13 scsi problems. May not be the
long-term fix)
Signed-off-by: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Greg KH <greg@kroah.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'arch')
0 files changed, 0 insertions, 0 deletions