linux-kernel - Re: shm broken on MIPS in current -git

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAOLZvyHaXcQ0RK8SNX+tTtQ=fJsLq9LxpyszCF82sK985XWQJg@mail.gmail.com>
Date:	Mon, 1 Aug 2011 15:22:48 +0200
From:	Manuel Lauss <manuel.lauss@...glemail.com>
To:	Vasiliy Kulikov <segoon@...nwall.com>
Cc:	linux-kernel@...r.kernel.org,
	Linux-MIPS <linux-mips@...ux-mips.org>
Subject: Re: shm broken on MIPS in current -git

On Mon, Aug 1, 2011 at 3:11 PM, Vasiliy Kulikov <segoon@...nwall.com> wrote:
> On Mon, Aug 01, 2011 at 14:51 +0200, Manuel Lauss wrote:
>> Commits 5774ed014f02120db9a6945a1ecebeb97c2acccb
>> (shm: handle separate PID namespaces case)
>> and 4c677e2eefdba9c5bfc4474e2e91b26ae8458a1d
>> (shm: optimize locking and ipc_namespace getting)
>> break on my MIPS systems.
>
> Can you please identify what commit breaks the system?

Reverting this one fixes the oops for good:

5774ed014f02120db9a6945a1ecebeb97c2acccb
 (shm: handle separate PID namespaces case)


>>  The following oops is
>> printed on boot, and as a result, more than  300 zombie kworker
>> kernel processes are resident.  I don't see this oops on x86 or x64.
>
> Do you have the same configs for x86 and mips?

MIPS is UP, SLAB without preempt, x86 is UP/SMP, SLUB with preempt.
It's not SLAB/SLUB and not preempt, and both MIPS+x86 have all
namespace options enabled.

both configs are temporarily available here:
http://mlau.at/config-mips
http://mlau.at/config-x64

Thanks!
     Manuel Lauss
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/