Re: possible deadlock in aio_poll

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Miklos Szeredi <miklos@xxxxxxxxxx>
Subject: Re: possible deadlock in aio_poll
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Mon, 10 Sep 2018 23:33:35 -0700
Cc: Christoph Hellwig <hch@xxxxxxxxxxxxx>, syzbot <syzbot+5b1df0420c523b45a953@xxxxxxxxxxxxxxxxxxxxxxxxx>, bcrl <bcrl@xxxxxxxxx>, linux-aio <linux-aio@xxxxxxxxx>, linux-fsdevel@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, syzkaller-bugs <syzkaller-bugs@xxxxxxxxxxxxxxxx>, Al Viro <viro@xxxxxxxxxxxxxxxxxx>, Andrea Arcangeli <aarcange@xxxxxxxxxx>, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
In-reply-to: <CAJfpeguWqJgU8EfjvOtsBYRbbY2J7Ck2oNUcLNS8my9g2eNZfA@mail.gmail.com>
User-agent: Mutt/1.9.2 (2017-12-15)

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.

Follow-Ups:
- Re: possible deadlock in aio_poll
  - From: Miklos Szeredi

References:
- possible deadlock in aio_poll
  - From: syzbot
- Re: possible deadlock in aio_poll
  - From: Christoph Hellwig
- Re: possible deadlock in aio_poll
  - From: Miklos Szeredi

Prev by Date: Re: [PATCH dhowells/mount-api] fs: fix checking an error code of security_fs_context_parse_param
Next by Date: Is it possible to add pid and comm members to the event structure to increase the display of user and thread information?
Previous by thread: Re: possible deadlock in aio_poll
Next by thread: Re: possible deadlock in aio_poll
Index(es):
- Date
- Thread

[Index of Archives] [Linux Ext4 Filesystem] [Union Filesystem] [Filesystem Testing] [Ceph Users] [Ecryptfs] [AutoFS] [Kernel Newbies] [Share Photos] [Security] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux Cachefs] [Reiser Filesystem] [Linux RAID] [Samba] [Device Mapper] [CEPH Development]