linux-kernel - Re: [patch] block: fix off-by-one in init_page

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] [day] [month] [year] [list]

Message-ID: <20120621154518.GR2753@decadent.org.uk>
Date:	Thu, 21 Jun 2012 16:45:18 +0100
From:	Ben Hutchings <ben@...adent.org.uk>
To:	Jeff Moyer <jmoyer@...hat.com>
Cc:	Jens Axboe <jaxboe@...ionio.com>, linux-kernel@...r.kernel.org,
	stable@...r.kernel.org, torsten.hilbrich@...unet.com,
	Nick Piggin <npiggin@...nel.dk>
Subject: Re: [patch] block: fix off-by-one in init_page_buffers

On Wed, Jun 20, 2012 at 02:01:28PM -0400, Jeff Moyer wrote:
[...]
> This needs backporting to the stable trees where the offending commit
> was backported.  I'm sure that includes 3.0 and 3.3, but not sure where
> else it was committed.

3.2 as well.

> Is there an easy way to tell what trees got the commit?
[...]

I don't know about easy, but if you have 'stable' as a remote then
this works:

$ git branch -r | sed 's/^ *stable\/linux-\([0-9.]*\)\.y/\1/; t; d' | while read version; do git rev-list --grep=080399aaaf3531f5b8761ec0ac30ff98891e8686 v$version..stable/linux-$version.y | grep -q . && echo $version; done
3.0
3.2
3.3

(Maybe I'll wrap that up in a script.)
 
Ben.

-- 
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
                                                              - Albert Camus
--
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/