linux-kernel - Re: [PATCH v2 1/2] loop: Report EOPNOTSUPP properly

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: <1549577503.153283.0.camel@acm.org>
Date:   Thu, 07 Feb 2019 14:11:43 -0800
From:   Bart Van Assche <bvanassche@....org>
To:     Evan Green <evgreen@...omium.org>, Jens Axboe <axboe@...nel.dk>
Cc:     Gwendal Grignou <gwendal@...omium.org>,
        Martin K Petersen <martin.petersen@...cle.com>,
        Alexis Savery <asavery@...omium.org>,
        Ming Lei <ming.lei@...hat.com>, linux-block@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 1/2] loop: Report EOPNOTSUPP properly

On Thu, 2019-02-07 at 12:57 -0800, Evan Green wrote:
> Properly plumb out EOPNOTSUPP from loop driver operations, which may
> get returned when for instance a discard operation is attempted but not
> supported by the underlying block device. Before this change, everything
> was reported in the log as an I/O error, which is scary and not
> helpful in debugging.

Reviewed-by: Bart Van Assche <bvanassche@....org>