All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Luis Chamberlain <mcgrof@kernel.org>,
	Chaitanya Kulkarni <kch@nvidia.com>
Cc: linux-block@vger.kernel.org, Pankaj Raghav <pankydev8@gmail.com>,
	Adam Manzanares <a.manzanares@samsung.com>,
	Nitesh Shetty <nj.shetty@samsung.com>
Subject: Re: block loopback driver possible regression since next-20220211
Date: Sat, 19 Feb 2022 09:18:58 -0700	[thread overview]
Message-ID: <cfce5ca9-e845-4b56-e33d-283fee37c3aa@kernel.dk> (raw)
In-Reply-To: <YhBfsIqCNsi7D/st@bombadil.infradead.org>

On 2/18/22 8:10 PM, Luis Chamberlain wrote:
> I noticed that since next-20220211 losetup fails at something stupid
> simple:
> 
> losetup $LOOPDEV $DISK
> 
> I can't see how the changes on drivers/block/loop.c would cause this,
> I even tried to revert what I thought would be the only commit which
> would seem to do a functional change "loop: revert "make autoclear
> operation asynchronous" but that didn't fix it.
> 
> I proceeded to bisecting... but I did this on today's linux-next,
> and well today's linux-next is hosed even at boot. My bisection then
> was completley inconclusive since linux-next is pure poop today.
> 
> Any ideas though?
> 
> Fortunately Linus' tree is fine.
> 
> I'm quit afraid that we wouldn't have caught this issue. Seems pretty
> straight forward. It would seem we don't have such a basic thing on
> blktests, so I'll go add that...

My guess would be that it's:

commit fbdee71bb5d8d054e1bdb5af4c540f2cb86fe296
Author: Christoph Hellwig <hch@lst.de>
Date:   Tue Jan 4 08:16:47 2022 +0100

    block: deprecate autoloading based on dev_t

-- 
Jens Axboe


  parent reply	other threads:[~2022-02-19 16:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-19  3:10 block loopback driver possible regression since next-20220211 Luis Chamberlain
2022-02-19  3:32 ` Luis Chamberlain
2022-02-19 16:18 ` Jens Axboe [this message]
2022-02-19 19:05   ` Luis Chamberlain
2022-02-20 17:24     ` Chaitanya Kulkarni
2022-02-22  8:53     ` Christoph Hellwig

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=cfce5ca9-e845-4b56-e33d-283fee37c3aa@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=a.manzanares@samsung.com \
    --cc=kch@nvidia.com \
    --cc=linux-block@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=nj.shetty@samsung.com \
    --cc=pankydev8@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.