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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <27472e91-046e-4160-85fe-b775d5ac02cd@zmail05.collab.prod.int.phx2.redhat.com>
Date:	Thu, 29 Sep 2011 16:00:05 -0400 (EDT)
From:	Doug Ledford <dledford@...hat.com>
To:	Andrew Morton <akpm00@...il.com>
Cc:	stable-review@...nel.org, torvalds@...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,
	Andrew Morton <akpm@...ux-foundation.org>,
	Greg KH <gregkh@...e.de>
Subject: Re: [159/244] ipc/mqueue.c: fix mq_open() return value

----- Original Message -----
> On Thu, 29 Sep 2011 12:08:55 -0700
> 
> Doug, the thing to do here is to rework your recent mqueue patchset.
> Prepare a minimal, critical-stuff series of bugfix patches against
> current Linus mainline which is also applicable to -stable.  We can
> merge that into 3.1 or, more likely, into 3.2-rc1/3.1.x.

The original patchset was against a clean Linus mainline, so that's already done.

> Then, later, we can merge up the less critical parts of that
> patchset.
> 
> otoh, the only not-applicable-to-stable part of that patchset appears
> to be "[1/5] ipc/mqueue: cleanup definition names and locations" and
> it's fairly small.  So we could perhaps just merge all five into
> 3.2-rc1, with a -stable backport.

That would be my suggestion.

> Doing that backport would require that we first backport the buggy
> patches (ie: this one), which is a bit weird.  Perhaps it would be
> better for you to prepare a reworked patch series for 3.0.x after
> that five-patch series hits mainline.

That or drop the buggy patch from -stable then fix it all in one go.

-- 
Doug Ledford <dledford@...hat.com>
              GPG KeyID: CFBFF194
	      http://people.redhat.com/dledford

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