Bug 11929
Summary: | CIFS error results in a kernel oops from cifs_mount | ||
---|---|---|---|
Product: | File System | Reporter: | Brandon Ehle (azverkan) |
Component: | CIFS | Assignee: | Steve French (sfrench) |
Status: | RESOLVED PATCH_ALREADY_AVAILABLE | ||
Severity: | normal | CC: | jlayton, shirishp |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.27 | Subsystem: | |
Regression: | --- | Bisected commit-id: |
Description
Brandon Ehle
2008-10-31 18:10:51 UTC
Is this recreatable? What are the steps that lead up to this oops? This may be due to the mount/umount races that were fixed last fall. Those *should* be fixed now in both >= 2.6.28 and in recent 2.6.27 stable kernels. Can you let us know whether you're still seeing this on more recent kernels? I agree with Jeff - any lock related conflicts in this area were likely to have been cleared by the mount fixes which went into mainline and also into 2.6.27.9 (or later) stable kernel series. Any occurrences at that level or later (2.6.27.9 or later)? The machine that I reproduced this on a couple times is now on 2.6.29-rc5 and I haven't seen the problem, but I haven't been using CIFS as much lately. OK - please reopen this (or a new defect) if you see anything similar in the future. The locking in this area is much better and it is very likely the problem was resolved by that patch series. |