linux-kernel - Re: next-20130117 - kernel BUG with aio

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: <CAJd=RBBBbv07aoOTF=PNy1FpCyuRV7fnQEGX_DXEYFSSknKtqQ@mail.gmail.com>
Date:	Tue, 22 Jan 2013 21:43:27 +0800
From:	Hillf Danton <dhillf@...il.com>
To:	Valdis Kletnieks <Valdis.Kletnieks@...edu>
Cc:	Benjamin LaHaise <bcrl@...ck.org>,
	Kent Overstreet <koverstreet@...gle.com>,
	linux-kernel@...r.kernel.org, linux-aio@...ck.org
Subject: Re: next-20130117 - kernel BUG with aio

On Mon, Jan 21, 2013 at 9:24 PM, Valdis Kletnieks
<Valdis.Kletnieks@...edu> wrote:
> Am seeing a reproducible BUG in the kernel with next-20130117
> whenever I fire up VirtualBox.  Unfortunately, I hadn't done that
> in a while, so the last 'known good' kernel was next-20121203.
>
> I'm strongly suspecting one of Kent Overstreet's 32 patches against aio,
> because 'git blame' shows those landing on Jan 12, and not much else
> happening to fs/aio.c in ages.
>
Take a try?
---
--- a/fs/aio.c	Tue Jan 22 21:37:54 2013
+++ b/fs/aio.c	Tue Jan 22 21:43:58 2013
@@ -683,6 +683,9 @@ static inline void kioctx_ring_unlock(st
 {
 	struct aio_ring *ring;

+	if (!ctx)
+		return;
+
 	smp_wmb();
 	/* make event visible before updating tail */

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