All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Linux regressions mailing list <regressions@lists.linux.dev>
Cc: Josef Bacik <josef@toxicpanda.com>,
	David Sterba <dsterba@suse.com>, Chris Mason <clm@fb.com>,
	linux-btrfs <linux-btrfs@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Wyatt Childers <kernel.dbwta@haxing.ninja>,
	pmacedo@gmail.com
Subject: Re: [Regression] Bug 216961 - Severe IO scheduling starvation issues with btrfs
Date: Tue, 28 Feb 2023 20:40:39 +0100	[thread overview]
Message-ID: <20230228194039.GP10580@suse.cz> (raw)
In-Reply-To: <06a5ada1-d1b8-3139-3a60-f43958f90f79@leemhuis.info>

On Fri, Feb 17, 2023 at 06:17:58AM +0100, Linux regression tracking (Thorsten Leemhuis) wrote:
> On 16.02.23 23:39, Josef Bacik wrote:
> > On Thu, Feb 16, 2023 at 12:43 PM Thorsten Leemhuis
> > <regressions@leemhuis.info> wrote:
> >>
> >> Hi btrfs maintainers and developers.
> >>
> >> I might be missing something, but it looks like the report was ignored.
> >> Is there a reason for that?
> > 
> > Mostly just being blind.
> 
> Happens.
> 
> >  I've responded to the BZ, I'll investigate
> > through the BZ.

According to the bug it's a problem in BFQ.

  reply	other threads:[~2023-02-28 19:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-26 11:17 [Regression] Bug 216961 - Severe IO scheduling starvation issues with btrfs Linux kernel regression tracking (Thorsten Leemhuis)
2023-02-16 17:43 ` Thorsten Leemhuis
2023-02-16 22:39   ` Josef Bacik
2023-02-17  5:17     ` Linux regression tracking (Thorsten Leemhuis)
2023-02-28 19:40       ` David Sterba [this message]
2023-03-01  7:34         ` Linux regression tracking (Thorsten Leemhuis)

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=20230228194039.GP10580@suse.cz \
    --to=dsterba@suse.cz \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=josef@toxicpanda.com \
    --cc=kernel.dbwta@haxing.ninja \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmacedo@gmail.com \
    --cc=regressions@lists.linux.dev \
    /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.