linux-kernel - Re: [PATCH] aio: clean up aio ring in the fail path

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: <20131206153413.GA31613@redhat.com>
Date:	Fri, 6 Dec 2013 10:34:13 -0500
From:	Dave Jones <davej@...hat.com>
To:	Benjamin LaHaise <bcrl@...ck.org>
Cc:	Gu Zheng <guz.fnst@...fujitsu.com>, linux-aio@...ck.org,
	fsdevel <linux-fsdevel@...r.kernel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Al Viro <viro@...iv.linux.org.uk>, Kent <kmo@...erainc.com>,
	Kristian Nielsen <knielsen@...elsen-hq.org>
Subject: Re: [PATCH] aio: clean up aio ring in the fail path

On Fri, Dec 06, 2013 at 10:26:54AM -0500, Benjamin LaHaise wrote:
 > On Wed, Dec 04, 2013 at 06:19:06PM +0800, Gu Zheng wrote:
 > > Clean up the aio ring file in the fail path of aio_setup_ring
 > > and ioctx_alloc. And maybe it can fix the GPF issue reported by
 > > Dave Jones:
 > > https://lkml.org/lkml/2013/11/25/898
 > 
 > Good catch.  I've applied this to my aio-next tree.  It does indeed look 
 > like it could be the cause of Dave's GPF -- I'll try to trigger it with 
 > some other kernel debug options on and see if the EAGAIN failure case can 
 > trip it up.

I think I forgot to reply and let you know this seems to fix it for me.

	Dave

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