[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191025001750.GE31224@sasha-vm>
Date: Thu, 24 Oct 2019 20:17:50 -0400
From: Sasha Levin <sashal@...nel.org>
To: Alessio Balsini <balsini@...roid.com>
Cc: gregkh@...uxfoundation.org, stable@...r.kernel.org,
linux-kernel@...r.kernel.org, kernel-team@...roid.com,
Jens Axboe <axboe@...nel.dk>
Subject: Re: [PATCH 4.4 4.9 4.14] loop: Add LOOP_SET_DIRECT_IO to compat ioctl
On Wed, Oct 23, 2019 at 06:17:36PM +0100, Alessio Balsini wrote:
>[ Upstream commit fdbe4eeeb1aac219b14f10c0ed31ae5d1123e9b8 ]
>
>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.
>
>Cc: Jens Axboe <axboe@...nel.dk>
>Signed-off-by: Alessio Balsini <balsini@...roid.com>
>Signed-off-by: Jens Axboe <axboe@...nel.dk>
>Signed-off-by: Sasha Levin <sashal@...nel.org>
Queued up, thanks!
--
Thanks,
Sasha
Powered by blists - more mailing lists