linux-kernel - Re: user namespace: make signal.c respect user namespaces (v5)

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20111119004302.GB16259@sergelap>
Date:	Fri, 18 Nov 2011 18:43:02 -0600
From:	Serge Hallyn <serge.hallyn@...onical.com>
To:	"Eric W. Biederman" <ebiederm@...ssion.com>
Cc:	"Serge E. Hallyn" <serge@...lyn.com>, richard@....at,
	containers@...ts.linux-foundation.org,
	linux-kernel@...r.kernel.org, eparis@...hat.com, oleg@...hat.com,
	dhowells@...hat.com, Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: user namespace: make signal.c respect user namespaces (v5)

Quoting Eric W. Biederman (ebiederm@...ssion.com):
> "Serge E. Hallyn" <serge.hallyn@...onical.com> writes:
> 
> > Quoting Eric W. Biederman (ebiederm@...ssion.com):
> >> There is a small bug here.  You want to fixup q->info, not info.
> >> Otherwise you might try dereferencing one of the special signals and get
> >> a NULL pointer dereference.
> >
> > Thanks, Eric.  Oddly I've not seen this happen in quite a bit of
> > testing with the kernel, but you certainly must be right.  I sent
> > out a new patch to fix that.
> 
> You clearly have a different test case than I do.

I ran a good chunk of ltp...  and it passed.  I can't explain it.
 
> I managed to trigger the oops  within about 5 minutes of just fooling
> around.
> 
> You want to say &q->info not q->info in your updated patch.

Oh, yes, thanks.  Sorry, I shouldn't have sent that one as I wasn't able
to compile and test until tonight.

-serge
--
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/