[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180911063335.GA3315@infradead.org>
Date: Mon, 10 Sep 2018 23:33:35 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Miklos Szeredi <miklos@...redi.hu>
Cc: Christoph Hellwig <hch@...radead.org>,
syzbot <syzbot+5b1df0420c523b45a953@...kaller.appspotmail.com>,
bcrl <bcrl@...ck.org>, linux-aio <linux-aio@...ck.org>,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
syzkaller-bugs <syzkaller-bugs@...glegroups.com>,
Al Viro <viro@...iv.linux.org.uk>,
Andrea Arcangeli <aarcange@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: possible deadlock in aio_poll
On Mon, Sep 10, 2018 at 08:14:20PM +0200, Miklos Szeredi wrote:
> Why do pollable waitqueues need to disable interrupts generally?
Any waitqueue needs to disable interrupts for consistency. We
always use spin_lock_irqsave in __wake_up_common_lock() for example.
Powered by blists - more mailing lists