Bug 26272
Summary: | BUG: Scheduling while atomic in fuse_notify_inval_entry | ||
---|---|---|---|
Product: | File System | Reporter: | Nikolaus Rath (Nikolaus) |
Component: | Other | Assignee: | fs_other |
Status: | RESOLVED CODE_FIX | ||
Severity: | normal | CC: | alan |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.35-23-generic | Subsystem: | |
Regression: | No | Bisected commit-id: | |
Attachments: |
dmesg output after reproducing bug
contents of /sys/kernel/debug/tracing/trace after reproducing bug |
Description
Nikolaus Rath
2011-01-07 00:52:46 UTC
I have learned that the following is useful for debugging "scheduling while atomic" bugs. The respective files are attached: $ sudo sh -c "echo 1 > /sys/kernel/debug/tracing/options/latency-format" $ sudo sh -c "echo 1 > /sys/kernel/debug/tracing/tracing_enabled" $ sudo sh -c "echo 1 > /sys/kernel/debug/tracing/tracing_on" $ sudo sh -c "echo function > /sys/kernel/debug/tracing/current_tracer" (reproduced bug) $ bzip2 -c /sys/kernel/debug/tracing/trace > trace.bz2 $ dmesg | bzip2 > dmesg.bz2 Created attachment 42852 [details]
dmesg output after reproducing bug
Created attachment 42862 [details]
contents of /sys/kernel/debug/tracing/trace after reproducing bug
Bug seems to exist in 2.6.35, but not in 2.6.37-rc2. |