From: Randy Dunlap <rdunlap@infradead.org>
To: Borislav Petkov <bp@alien8.de>,
Johannes Thumshirn <johannes.thumshirn@wdc.com>,
Damien Le Moal <Damien.LeMoal@wdc.com>
Cc: Christoph Hellwig <hch@lst.de>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Hannes Reinecke <hare@suse.de>, Jens Axboe <axboe@kernel.dk>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: first bad commit: [5795eb443060148796beeba106e4366d7f1458a6] scsi: sd_zbc: emulate ZONE_APPEND commands
Date: Fri, 11 Sep 2020 15:22:15 -0700 [thread overview]
Message-ID: <d7549a8f-ec57-7cee-577e-902f70c8bd42@infradead.org> (raw)
In-Reply-To: <20200911221759.GA2869@nazgul.tnic>
On 9/11/20 3:17 PM, Borislav Petkov wrote:
> On Fri, Sep 11, 2020 at 09:53:12PM +0200, Borislav Petkov wrote:
>> Now, looking at that patch:
>>
>> 5795eb443060 ("scsi: sd_zbc: emulate ZONE_APPEND commands")
>>
>> yeah, that doesn't revert cleanly. But it talks about zoned-something
>> devices and that rings a bell because you guys broke my zoned device
>> once already:
>
> Ok, so Johannes and I poked a bit on IRC and here it is:
>
> # CONFIG_BLK_DEV_ZONED is not set.
>
> Enabling it, fixes the issue.
>
Uh, you are not saying that enabling that CONFIG_ is the final fix, are you?
If so, do I need to enable it, even if I don't have a zoned block device?
--
~Randy
next prev parent reply other threads:[~2020-09-11 22:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 19:53 Borislav Petkov
2020-09-11 22:17 ` Borislav Petkov
2020-09-11 22:22 ` Randy Dunlap [this message]
2020-09-11 22:26 ` Johannes Thumshirn
2020-09-11 22:38 ` Randy Dunlap
2020-09-11 23:07 ` Borislav Petkov
2020-09-12 2:31 ` Damien Le Moal
2020-09-12 8:37 ` Borislav Petkov
2020-09-12 12:18 ` Damien Le Moal
2020-09-12 13:05 ` Borislav Petkov
2020-09-12 9:09 ` Johannes Thumshirn
2020-09-12 12:59 ` Damien Le Moal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d7549a8f-ec57-7cee-577e-902f70c8bd42@infradead.org \
--to=rdunlap@infradead.org \
--cc=Damien.LeMoal@wdc.com \
--cc=axboe@kernel.dk \
--cc=bp@alien8.de \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=johannes.thumshirn@wdc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.petersen@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®