From: Salvatore Bonaccorso <carnil@debian.org>
To: Christian Hesse <list@eworm.de>
Cc: Roland Clobus <rclobus@rclobus.nl>,
Lizhi Xu <lizhi.xu@windriver.com>, Christoph Hellwig <hch@lst.de>,
Jens Axboe <axboe@kernel.dk>,
1106070@bugs.debian.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
regressions@lists.linux.dev
Subject: Re: [6.12.y regression] loosetup: failed to set up loop device: Invalid argument after 184b147b9f7f ("loop: Add sanity check for read/write_iter")
Date: Tue, 20 May 2025 09:16:05 +0200 [thread overview]
Message-ID: <aCwsNSEoxfs4DOvi@eldamar.lan> (raw)
In-Reply-To: <20250520083438.295e415a@leda.eworm.net>
H Christian,
On Tue, May 20, 2025 at 08:34:38AM +0200, Christian Hesse wrote:
> Salvatore Bonaccorso <carnil@debian.org> on Tue, 2025/05/20 07:57:
> > In Debian Roland Clobus reported a regression with setting up loop
> > devices from a backing squashfs file lying on read-only mounted target
> > directory from a iso.
> >
> > The original report is at:
> > https://bugs.debian.org/1106070
>
> We are suffering the same for Arch Linux. Already reported here:
>
> https://lore.kernel.org/all/20250519175640.2fcac001@leda.eworm.net/
Sorry missed that one! Ack, so let's continue in that thread (worth
looping in the regressions list though?)
Regards,
Salvatore
next prev parent reply other threads:[~2025-05-20 7:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3a333f27-6810-4313-8910-485df652e897@rclobus.nl>
2025-05-20 5:57 ` [6.12.y regression] loosetup: failed to set up loop device: Invalid argument after 184b147b9f7f ("loop: Add sanity check for read/write_iter") Salvatore Bonaccorso
2025-05-20 6:10 ` Salvatore Bonaccorso
2025-05-20 6:34 ` Christian Hesse
2025-05-20 7:16 ` Salvatore Bonaccorso [this message]
2025-05-20 15:23 ` Jens Axboe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aCwsNSEoxfs4DOvi@eldamar.lan \
--to=carnil@debian.org \
--cc=1106070@bugs.debian.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=list@eworm.de \
--cc=lizhi.xu@windriver.com \
--cc=rclobus@rclobus.nl \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox