[Bugme-new] [Bug 40882] New: Weird error with jfs and PaX-enabled kernel(memleak).

bugzilla-daemon at bugzilla.kernel.org bugzilla-daemon at bugzilla.kernel.org
Wed Aug 10 09:46:46 PDT 2011


https://bugzilla.kernel.org/show_bug.cgi?id=40882

           Summary: Weird error with jfs and PaX-enabled kernel(memleak).
           Product: File System
           Version: 2.5
    Kernel Version: 2.6.38
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: JFS
        AssignedTo: shaggy at linux.vnet.ibm.com
        ReportedBy: librarian_rus at yahoo.com
        Regression: No


Hello!

I am running Gentoo hardened amd64 and grsecurity/PaX-enabled kernel 2.6.38: 
(2.6.38-hardened-r6-Plasma #1 SMP Wed Jul 27 19:44:47 MSD 2011 x86_64
Pentium(R) Dual-Core CPU E5300 @ 2.60GHz GenuineIntel GNU/Linux). However,
grsecurity RBAC is disabled in kernel config but PaX features are enabled
(kernel config provided below). Also I have JFS filesystem on my /usr, /var and
/. They are LVM volumes over software(dm) RAID-5 over 4 harddrives.
The issue happens when I'm running ls -la /usr/bin:
~ # ls -la /usr/bin/
Killed
It just returns this "Killed". Parts of log messages from kern.log and pax.log
attached below. The PaX system complains about memory leak attempt, but running
"ls -la /" or "ls -la /var/log" or even "ls -la /usr" and "ls -la /usr/src"
causes no problems, which is weird. 
Another issue happens with AIDE. If I specify any directory one level below of
/usr like "/usr/bin" it fails to create database with the same "Killed", but
when I use syntax like "/usr//bin" everything is OK. With two levels below like
"/usr/local/bin" everything is ok. The produced traces and errors are
word-to-word identical so this issues are seem to be connected.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


More information about the Bugme-new mailing list