From: Borislav Petkov <bp@alien8.de>
To: Damien Le Moal <Damien.LeMoal@wdc.com>
Cc: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>,
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: Sat, 12 Sep 2020 15:05:15 +0200 [thread overview]
Message-ID: <20200912130515.GB3678@zn.tnic> (raw)
In-Reply-To: <CY4PR04MB3751C8FA76C49708370E928DE7250@CY4PR04MB3751.namprd04.prod.outlook.com>
On Sat, Sep 12, 2020 at 12:18:52PM +0000, Damien Le Moal wrote:
> But it was Thunderbird, getting real plain text emails with outlook is
> impossible.
Yeap.
> Corruption I think came from the copy-paste from the Mac bash
> terminal... Tabs get replaced by spacers.
Yeah, never copy-paste hunks. I go "git diff > /tmp/diff" and then load
it into the editor which has the mail opened ":r /tmp/diff" (vim).
> Host-managed is still a thing, getting bigger. But host-aware never really
> gained a lot of traction due to, I think, the potentially very weird performance
> profile they can get into (Hmmm... similar to recent drive-managed noise...)
Yeah, I had the suspicion that it would be some raisins like that.
> No worries, we will fix the mess (sorry we hit you again !).
Yeah, thanks and no probs.
> The patch was space corrupted, but could you still try it ? Did it solve your
> problem ? I can recend it (minus space corruption) if needed.
Yeah, I see
[ 3.263400] ata4: SATA max UDMA/133 abar m131072@0xfe380000 port 0xfe380280 irq 45
[ 4.943083] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 4.951590] ata4.00: NCQ Send/Recv Log not supported
[ 4.961868] ata4.00: ATA-10: ST8000AS0022-1WL17Z, SN01, max UDMA/133
[ 4.977167] ata4.00: 15628053168 sectors, multi 16: LBA48 NCQ (depth 32), AA
[ 4.987217] ata4.00: NCQ Send/Recv Log not supported
[ 5.004230] ata4.00: configured for UDMA/133
but no "sdc" device or a partition or so. So I can't even do fdisk -l on it.
I see your other version - I'll test that later because real life awaits
and it is weekend and so on...
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2020-09-12 13:05 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
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 [this message]
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=20200912130515.GB3678@zn.tnic \
--to=bp@alien8.de \
--cc=Damien.LeMoal@wdc.com \
--cc=Johannes.Thumshirn@wdc.com \
--cc=axboe@kernel.dk \
--cc=hare@suse.de \
--cc=hch@lst.de \
--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®