linux-ext4 - Re: [PATCH 24/27] block: remove QUEUE_FLAG

lists.openwall.net		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 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20220410062620.GA16234@lst.de>
Date:   Sun, 10 Apr 2022 08:26:20 +0200
From:   Christoph Hellwig <hch@....de>
To:     Christoph Böhmwalder 
        <christoph.boehmwalder@...bit.com>
Cc:     Christoph Hellwig <hch@....de>, dm-devel@...hat.com,
        linux-xfs@...r.kernel.org, linux-fsdevel@...r.kernel.org,
        linux-um@...ts.infradead.org, linux-block@...r.kernel.org,
        drbd-dev@...ts.linbit.com, nbd@...er.debian.org,
        ceph-devel@...r.kernel.org,
        virtualization@...ts.linux-foundation.org,
        xen-devel@...ts.xenproject.org, Jens Axboe <axboe@...nel.dk>,
        linux-bcache@...r.kernel.org, linux-raid@...r.kernel.org,
        linux-mmc@...r.kernel.org, linux-mtd@...ts.infradead.org,
        linux-nvme@...ts.infradead.org, linux-s390@...r.kernel.org,
        linux-scsi@...r.kernel.org, target-devel@...r.kernel.org,
        linux-btrfs@...r.kernel.org, linux-ext4@...r.kernel.org,
        linux-f2fs-devel@...ts.sourceforge.net, cluster-devel@...hat.com,
        jfs-discussion@...ts.sourceforge.net, linux-nilfs@...r.kernel.org,
        ntfs3@...ts.linux.dev, ocfs2-devel@....oracle.com,
        linux-mm@...ck.org,
        "Martin K . Petersen" <martin.petersen@...cle.com>,
        Coly Li <colyli@...e.de>
Subject: Re: [PATCH 24/27] block: remove QUEUE_FLAG_DISCARD

On Sat, Apr 09, 2022 at 10:15:33AM +0200, Christoph Böhmwalder wrote:
> On 09.04.22 06:50, Christoph Hellwig wrote:
>> Just use a non-zero max_discard_sectors as an indicator for discard
>> support, similar to what is done for write zeroes.
>>
>> The only places where needs special attention is the RAID5 driver,
>> which must clear discard support for security reasons by default,
>> even if the default stacking rules would allow for it.
>>
>> Signed-off-by: Christoph Hellwig <hch@....de>
>> Reviewed-by: Martin K. Petersen <martin.petersen@...cle.com>
>> Acked-by: Christoph Böhmwalder <christoph.boehmwalder@...bit.com> [btrfs]
>
> I think you may have a typo there: my ACK was for drbd, not btrfs.

Indeed, sorry.