linux-kernel - Re: [PATCH 00/10] ipc MSG

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: <20130228154620.a6d87ad8.akpm@linux-foundation.org>
Date:	Thu, 28 Feb 2013 15:46:20 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Peter Hurley <peter@...leysoftware.com>
Cc:	Stanislav Kinsbursky <skinsbursky@...allels.com>,
	linux-kernel@...r.kernel.org, Dave Jones <davej@...hat.com>
Subject: Re: [PATCH 00/10] ipc MSG_COPY fixes

On Mon, 25 Feb 2013 21:21:37 -0500
Peter Hurley <peter@...leysoftware.com> wrote:

> Over the weekend testing with trinity on KVM, I hit a similar oops
> (pasted below) to what others have already reported here
>      http://lkml.indiana.edu/hypermail/linux/kernel/1302.2/01465.html
> 
> While trying to uncover the underlying cause of the list corruption,
> I uncovered two other bugs which are addressed in
>   ipc: Fix potential oops when src msg > 4k w/ MSG_COPY
>   ipc: Don't allocate a copy larger than max
> 
> The other cleanup was incidental to trying to uncover the oops (so far
> unsuccessfully).

afacit, only the above two are needed in 3.9 and 3.8.x, agree?

The changelog for "ipc: Don't allocate a copy larger than max" is
rather poor - it doesn't actually describe the bug's effects, so people
will have trouble understanding whether they need the patch in their
kernels.  Can you please send along some additional description of this
one?


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