linux-kernel - Re: aio: kernel BUG at fs/aio.c:646!

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]

Date:	Mon, 5 Aug 2013 12:08:28 -0400
From:	Benjamin LaHaise <bcrl@...ck.org>
To:	Sasha Levin <sasha.levin@...cle.com>
Cc:	koverstreet@...gle.com, axboe@...nel.dk,
	Andrew Morton <akpm@...ux-foundation.org>,
	torvalds@...ux-foundation.org, LKML <linux-kernel@...r.kernel.org>,
	linux-aio@...ck.org, trinity@...r.kernel.org
Subject: Re: aio: kernel BUG at fs/aio.c:646!

Hi Sasha,

On Mon, Aug 05, 2013 at 09:57:08AM -0400, Sasha Levin wrote:
> Hi all,
> 
> While fuzzing with trinity inside a KVM tools guest running latest -next 
> kernel,
> I've stumbled on the following spew caused by a new BUG() added in "aio: fix
> io_destroy() regression by using call_rcu()".

I did some investigating, and it looks like there is a problem with 
db446a08c23d5475e6b08c87acca79ebb20f283c (aio: convert the ioctx list to 
table lookup v3).  Can you confirm if reverting this patch eliminates 
the BUG() you're hitting?  In my testing, I wasn't able to trigger the 
BUG(), but I was able to trip up slab corruption with debugging on.  
Thanks,

		-ben

...
> Thanks,
> Sasha

-- 
"Thought is the essence of where you are now."
--
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/