[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <SN4PR0401MB3598033FF16A5AE1D375EDD69B4A0@SN4PR0401MB3598.namprd04.prod.outlook.com>
Date: Tue, 4 Aug 2020 14:31:22 +0000
From: Johannes Thumshirn <Johannes.Thumshirn@....com>
To: Coly Li <colyli@...e.de>,
"linux-block@...r.kernel.org" <linux-block@...r.kernel.org>
CC: "linux-bcache@...r.kernel.org" <linux-bcache@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Ming Lei <ming.lei@...hat.com>,
Hannes Reinecke <hare@...e.com>, Xiao Ni <xni@...hat.com>,
Bart Van Assche <bvanassche@....org>,
Christoph Hellwig <hch@....de>,
Enzo Matsumiya <ematsumiya@...e.com>,
Jens Axboe <axboe@...nel.dk>, Evan Green <evgreen@...omium.org>
Subject: Re: [PATCH] block: tolerate 0 byte discard_granularity in
__blkdev_issue_discard()
On 04/08/2020 16:23, Coly Li wrote:
> This is the procedure to reproduce the panic,
> # modprobe scsi_debug delay=0 dev_size_mb=2048 max_queue=1
> # losetup -f /dev/nvme0n1 --direct-io=on
> # blkdiscard /dev/loop0 -o 0 -l 0x200
losetup -f /dev/sdX isn't it?
Powered by blists - more mailing lists