linux-kernel - Re: [159/244] ipc/mqueue.c: fix mq

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]

Date:	Thu, 29 Sep 2011 12:08:55 -0700
From:	Greg KH <gregkh@...e.de>
To:	Doug Ledford <dledford@...hat.com>
Cc:	stable-review@...nel.org, torvalds@...ux-foundation.org,
	akpm@...ux-foundation.org, alan@...rguk.ukuu.org.uk,
	Jiri Slaby <jslaby@...e.cz>,
	Manfred Spraul <manfred@...orfullife.com>,
	linux-kernel@...r.kernel.org, stable@...nel.org
Subject: Re: [159/244] ipc/mqueue.c: fix mq_open() return value

On Thu, Sep 29, 2011 at 02:51:51PM -0400, Doug Ledford wrote:
> ----- Original Message -----
> > Um, that's the way this patch is upstream, right?  So perhaps it
> > should
> > be fixed there first and then I can take the fix into -stable?
> 
> Upstream is a bit of a fuzzy statement ;-)  It might be in -next, but
> it's not in Linus' tree or Andrew's -mm tree or else my recent patches
> would have conflicted.

Sorry, I ment Linus's tree, that's where it matters for the stable
releases.

> And in fact, upon further reflection, I think maybe that particular
> test could use being split into two distinct tests.  One for wrapping
> the byte counter, which would return -ENOMEM, and one for exceeding
> RLIMIT_MSGQUEUE which would return -EPERM (not sure if that's right, I
> would have to poke around elsewhere, but it seems a better response
> when you are violating a ulimit than nomem to me anyway).

Ok, care to get the patch into Linus's tree and then I can take it into
stable?

greg k-h
--
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/