[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b469f0ec-0185-c624-b967-5080d805040c@suse.de>
Date: Tue, 4 Aug 2020 22:34:25 +0800
From: Coly Li <colyli@...e.de>
To: Johannes Thumshirn <Johannes.Thumshirn@....com>,
"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 2020/8/4 22:31, Johannes Thumshirn wrote:
> 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?
>
In my case, I use a NVMe SSD as the backing device of the loop device.
Because I don't have a scsi lun.
And loading scsi_debug module seems necessary, otherwise the discard
process just hang and I cannot see the kernel panic (I don't know why yet).
Coly Li
Powered by blists - more mailing lists