Re: INFO: rcu detected stall in blkdev_ioctl

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

To: syzbot <syzbot+369c35474963daf8f8eea897ecf33cb6ad6c7ea2@xxxxxxxxxxxxxxxxxxxxxxxxx>, axboe@xxxxxxxxx, linux-block@xxxxxxxxxxxxxxx, syzkaller-bugs@xxxxxxxxxxxxxxxx
Subject: Re: INFO: rcu detected stall in blkdev_ioctl
From: Tetsuo Handa <penguin-kernel@xxxxxxxxxxxxxxxxxxx>
Date: Sat, 28 Apr 2018 17:57:35 +0900
Cc: akpm@xxxxxxxxxxxxxxxxxxxx, gregkh@xxxxxxxxxxxxxxxxxxx, hpa@xxxxxxxxx, kstewart@xxxxxxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, mingo@xxxxxxxxxx, npiggin@xxxxxxxxx, pombredanne@xxxxxxxx, tglx@xxxxxxxxxxxxx, x86@xxxxxxxxxx
In-reply-to: <0000000000001554a7056add26c6@google.com>
References: <94eb2c05a38090aaeb0560706bb5@google.com> <0000000000001554a7056add26c6@google.com>
User-agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0

Like I noted in a patch at

https://groups.google.com/d/msg/syzkaller-bugs/2Rw8-OM6IbM/PzdobV8kAgAJ

loop module is not thread safe. Can we use more global lock?

Follow-Ups:
- Re: INFO: rcu detected stall in blkdev_ioctl
  - From: Tetsuo Handa

References:
- Re: INFO: rcu detected stall in blkdev_ioctl
  - From: syzbot

Prev by Date: Re: [PATCH 0/3] scsi: scsi-mq: don't hold host_busy in IO path
Next by Date: INFO: task hung in blk_queue_enter
Previous by thread: Re: INFO: rcu detected stall in blkdev_ioctl
Next by thread: Re: INFO: rcu detected stall in blkdev_ioctl
Index(es):
- Date
- Thread

[Index of Archives] [Linux RAID] [Linux SCSI] [Linux ATA RAID] [IDE] [Linux Wireless] [Linux Kernel] [ATH6KL] [Linux Bluetooth] [Linux Netdev] [Kernel Newbies] [Security] [Git] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Device Mapper]

Powered by Linux