/sys/slab directory crashes applications

Bug #174965 reported by Simon Edwards
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned
linux-source-2.6.22 (Ubuntu)
Won't Fix
Undecided
Unassigned
lmms (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: linux-image-2.6.22-14-generic

Reading and listing the files in /sys/slab can cause applications to crash. The command "find /sys/slab | xargs cat" works until cat segfaults. The music program LMMS scans the root directory and /sys/slab at startup and crashes too. Viewing the /sys/slab in Krusader, crashes it too.

The problam appears to be the one discussed in this thread: http://ussg.iu.edu/hypermail/linux/kernel/0709.2/1886.html

Workaround: Doing a "chmod a-x /sys/slab" is enough to hide the directory so that LMMS can startup and run normally.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Hardy Heron Alpha series is currently under development and contains an updated version of the kernel. It would be helpful if you could test the latest Hardy Alpha release: http://www.ubuntu.com/testing . You should be able to then test the new kernel via the LiveCD. If you can, please verify if this bug still exists or not and report back your results. Thanks.

Changed in linux-source-2.6.22:
status: New → Incomplete
Revision history for this message
Colin Ian King (colin-king) wrote :

I've had a look at Hardy Heron Alpha 6 (2.6.24-11) and it appears it had the latest code to fix this problem with the slub allocator. I cannot re-produce it on my 2.6.24-11 kernel based installation, suggesting the fix works in the latest kernel.

I suggest trying Hardy Heron Alpha 6 and seeing if it resolves the problem. Please let us know if it helps.

Revision history for this message
Tobias Junghans (tobydox) wrote :

Works in Hardy due to new kernel.

Changed in lmms:
status: New → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
Tobias Junghans (tobydox) wrote :

This one is outdated for Hardy and Intrepid kernels so it can be closed.

Changed in linux:
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.