Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Subject: Re: [PATCH v2] loop: Add LOOP_SET_DIRECT_IO to compat ioctl
To:     Alessio Balsini <balsini@android.com>, linux-block@vger.kernel.org
Cc:     linux-kernel@vger.kernel.org, dvander@gmail.com, elsk@google.com,
        gregkh@linuxfoundation.org, joelaf@google.com,
        kernel-team@android.com
References: <CAJWu+oo=GrZ+SbA6=bboM4==TKXBsTRWkTrkWiZ55pqhJtgQqQ@mail.gmail.com>
 <20190807004828.28059-1-balsini@android.com>
From:   Jens Axboe <axboe@kernel.dk>
Message-ID: <4dc06fb1-df3c-5887-725a-0d20c3291528@kernel.dk>
Date:   Thu, 8 Aug 2019 20:39:40 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <20190807004828.28059-1-balsini@android.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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