lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Tue, 06 Dec 2016 01:04:54 +0100
From:   Nicolai Stange <>
To:     Nicolai Stange <>
Cc:     Christoph Hellwig <>,
        Jens Axboe <>,
        Chaitanya Kulkarni <>,
        Shaun Tancheff <>,
        Damien Le Moal <>,,
Subject: Re: [PATCH] block: fix unintended fallthrough in generic_make_request_checks()

Nicolai Stange <> writes:

> ---
> Applicable to next-20161202.
> Note that after this patch, I'm seeing a single
>  EXT4-fs (dm-1): Delayed block allocation failed for inode 2625094 at
>                  logical offset 2032 with max blocks 2 with error 121
> with 121 == EREMOTEIO
> This is because my SATA sda reports 0x20 (invalid command) back
> in response to 0x41 (WRITE_SAME).
> After this has happened, sd_done() disables "write same" once and for
> all, hence only this single message.
> I expect this to get fixed by

Just FYI: Not really, the (supposedly) corresponding commit has already
been in linux-next when I was testing: commit 0ce1b18c42a5 ("libata:
Some drives failing on SCT Write Same").

I sent separate patch for this issue:



Powered by blists - more mailing lists