From: Salvatore Bonaccorso <carnil@debian.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Michael Schaller <misch@google.com>,
axboe@kernel.dk, linux-block@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: New partition on loop device doesn't appear in /dev anymore with kernel 5.17.0 and newer (repro script included)
Date: Sun, 5 Jun 2022 12:00:10 +0200 [thread overview]
Message-ID: <Ypx+qusVyLJEEb/r@eldamar.lan> (raw)
In-Reply-To: <20220603132313.GA20886@lst.de>
Hi,
On Fri, Jun 03, 2022 at 03:23:13PM +0200, Christoph Hellwig wrote:
> On Fri, Jun 03, 2022 at 03:21:28PM +0200, Michael Schaller wrote:
> > Thank you, Christoph! <3
> >
> > Patch https://lore.kernel.org/all/20220527055806.1972352-1-hch@lst.de/
> > does indeed fix the issue.
> >
> > Could this patch also be backported to 5.17 and 5.18?
>
> It should get picked up automatically based on the fixes tag as soon
> as it hits mainline.
As it does not apply cleanly to older versions, this probably will
need a sperate turnaround, but AFAICS it's just because of
a0e286b6a5b6 ("loop: remove lo_refcount and avoid lo_mutex in ->open /
->release") changing context of the fourth hunk in
drivers/block/loop.c .
Regards,
Salvatore
next prev parent reply other threads:[~2022-06-05 10:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CALt099+y4-kJ0OqVeKaAjAbs4inOkR-WE0FmyiJRDc1-Ev9UKw@mail.gmail.com>
2022-06-03 12:49 ` New partition on loop device doesn't appear in /dev anymore with kernel 5.17.0 and newer (repro script included) Christoph Hellwig
2022-06-03 13:21 ` Michael Schaller
2022-06-03 13:23 ` Christoph Hellwig
2022-06-05 10:00 ` Salvatore Bonaccorso [this message]
2022-06-06 7:49 ` Christoph Hellwig
2022-06-09 4:27 ` Christoph Hellwig
2022-06-09 7:10 ` Michael Schaller
2022-06-21 7:55 ` Michael Schaller
2022-06-03 12:46 Michael Schaller
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=Ypx+qusVyLJEEb/r@eldamar.lan \
--to=carnil@debian.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=misch@google.com \
/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