public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Mike Snitzer <snitzer@kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	Christoph Hellwig <hch@infradead.org>
Subject: Re: [GIT PULL] Block updates for 6.9-rc1
Date: Mon, 11 Mar 2024 19:03:26 -0600	[thread overview]
Message-ID: <3a8cca38-8555-4d28-a1eb-731fd3e6db28@kernel.dk> (raw)
In-Reply-To: <Ze-hwnd3ocfJc9xU@redhat.com>

On 3/11/24 6:28 PM, Mike Snitzer wrote:
> On Mon, Mar 11 2024 at  8:21P -0400,
> Linus Torvalds <torvalds@linux-foundation.org> wrote:
> 
>> On Mon, 11 Mar 2024 at 17:02, Jens Axboe <axboe@kernel.dk> wrote:
>>>
>>> Just revert that commit it for now.
>>
>> Done.
>>
>> I have to say, this is *not* some odd config here. It's literally a
>> default Fedora setup with encrypted volumes.
>>
>> So the fact that this got reported after I merged this shows a
>> complete lack of testing.
> 
> Please see my other reply just now.  This breakage is new.  Obviously
> cryptsetup's testsuite is lacking too because there wasn't any issue
> for weeks now.

Yep, agree on that, if it breaks maybe the first few booting it with
dm-crypt, then the testing certainly should've caught it.

>> It also makes me suspect that you do all your performance-testing on
>> something that may show great performance, but isn't perhaps the best
>> thing to actually use.
>>
>> May I suggest you start looking at encrypted volumes, and do your
>> performance work on those for a while?
>>
>> Yes, it will suck to see the crypto overhead, but hey, it's also real
>> life for real loads, so...
> 
> All for Jens being made to suffer with dm-crypt but I think we need a
> proper root cause of what is happening for you and Johannes ;)

Hah, yes. Does current -git without that revert boot for you? I'm
assuming you have a dm-crypt setup on your laptop :-)

-- 
Jens Axboe


  reply	other threads:[~2024-03-12  1:03 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-10 20:30 [GIT PULL] Block updates for 6.9-rc1 Jens Axboe
2024-03-11 19:43 ` pr-tracker-bot
2024-03-11 23:50 ` Johannes Weiner
2024-03-11 23:53   ` Jens Axboe
2024-03-11 23:58   ` Linus Torvalds
2024-03-12  0:02     ` Jens Axboe
2024-03-12  0:21       ` Linus Torvalds
2024-03-12  0:28         ` Mike Snitzer
2024-03-12  1:03           ` Jens Axboe [this message]
2024-03-12  1:09           ` Christoph Hellwig
2024-03-12  1:17             ` Jens Axboe
2024-03-12  1:20               ` Linus Torvalds
2024-03-12  1:23                 ` Jens Axboe
2024-03-12  1:28                   ` Linus Torvalds
2024-03-12  1:37                     ` Jens Axboe
2024-03-12 16:39                       ` Keith Busch
2024-03-12 11:53                   ` Christoph Hellwig
2024-03-12 15:25                     ` Jens Axboe
2024-03-12 11:52                 ` Christoph Hellwig
2024-03-12 15:22             ` Mike Snitzer
2024-03-12 16:28               ` Keith Busch
2024-03-12 21:10               ` Christoph Hellwig
2024-03-12 22:22                 ` Mike Snitzer
2024-03-12 22:30                   ` Christoph Hellwig
2024-03-12 22:50                     ` Mike Snitzer
2024-03-12 22:58                       ` Christoph Hellwig
2024-04-11 20:15                         ` [PATCH for-6.10 0/2] dm: use late bio-splitting and queue_limits_set Mike Snitzer
2024-04-11 20:15                         ` [PATCH for-6.10 1/2] dm-crypt: stop constraining max_segment_size to PAGE_SIZE Mike Snitzer
2024-04-12  6:11                           ` Christoph Hellwig
2024-04-15 14:08                           ` Mikulas Patocka
2024-04-23  7:32                           ` Ming Lei
2024-04-11 20:15                         ` [PATCH for-6.10 2/2] dm: use queue_limits_set Mike Snitzer
2024-04-23  7:33                           ` Ming Lei
2024-03-13 13:11                 ` [GIT PULL] Block updates for 6.9-rc1 Ming Lei
2024-03-12  1:01         ` Jens Axboe
2024-03-12  0:25       ` Mike Snitzer

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=3a8cca38-8555-4d28-a1eb-731fd3e6db28@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=hannes@cmpxchg.org \
    --cc=hch@infradead.org \
    --cc=linux-block@vger.kernel.org \
    --cc=snitzer@kernel.org \
    --cc=torvalds@linux-foundation.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