[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210728091405.cqvkgv6c2vvsmacb@ws.net.home>
Date: Wed, 28 Jul 2021 11:14:05 +0200
From: Karel Zak <kzak@...hat.com>
To: Krzysztof Olędzki <ole@....pl>
Cc: Jens Axboe <axboe@...nel.dk>,
Sinan Kaya <sinan.kaya@...rosoft.com>,
util-linux@...r.kernel.org, linux-block@...r.kernel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Commit d5fd456c88aba4fcf77d35fe38024a8d5c814686 - "loopdev: use
LOOP_CONFIG ioctl" broke loop on x86-64 w/ 32 bit userspace
On Tue, Jul 27, 2021 at 10:46:06PM -0700, Krzysztof Olędzki wrote:
> So, to confirm - checking for both EINVAL and ENOTTY after LOOP_CONFIGURE is
> the proper way of taking care this?
>
> https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/tree/lib/loopdev.c?id=d4423cce9b9001c9de7ebc6f64f6cc2bb854944c#n1362
We need both to make losetup/mount robust for already released kernels.
Fixed: https://github.com/karelzak/util-linux/commit/583990d25b5d65a9a9771a39d112de0ee16a1f3a
Thanks for your report!
Karel
--
Karel Zak <kzak@...hat.com>
http://karelzak.blogspot.com
Powered by blists - more mailing lists