linux-kernel - Re: [PATCH v2] loop: Add LOOP_SET_DIRECT

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] [day] [month] [year] [list]

Message-ID: <4dc06fb1-df3c-5887-725a-0d20c3291528@kernel.dk>
Date:   Thu, 8 Aug 2019 20:39:40 -0700
From:   Jens Axboe <axboe@...nel.dk>
To:     Alessio Balsini <balsini@...roid.com>, linux-block@...r.kernel.org
Cc:     linux-kernel@...r.kernel.org, dvander@...il.com, elsk@...gle.com,
        gregkh@...uxfoundation.org, joelaf@...gle.com,
        kernel-team@...roid.com
Subject: Re: [PATCH v2] loop: Add LOOP_SET_DIRECT_IO to compat ioctl

On 8/6/19 5:48 PM, Alessio Balsini wrote:
> Enabling Direct I/O with loop devices helps reducing memory usage by
> avoiding double caching.  32 bit applications running on 64 bits systems
> are currently not able to request direct I/O because is missing from the
> lo_compat_ioctl.
> 
> This patch fixes the compatibility issue mentioned above by exporting
> LOOP_SET_DIRECT_IO as additional lo_compat_ioctl() entry.
> The input argument for this ioctl is a single long converted to a 1-bit
> boolean, so compatibility is preserved.

Applied, thanks.

-- 
Jens Axboe