stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kent Overstreet <kent.overstreet@linux.dev>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Sasha Levin <sashal@kernel.org>, Helge Deller <deller@kernel.org>,
	 stable@vger.kernel.org
Subject: Re: dddd
Date: Fri, 15 Mar 2024 22:44:43 -0400	[thread overview]
Message-ID: <v44t23xux6w4jrpcsh54z5r6ukya5afcgzmyczus4wkouszb5l@s2ofhjlwlz77> (raw)
In-Reply-To: <2024031516-chip-circulate-ff78@gregkh>

On Fri, Mar 15, 2024 at 07:27:23PM +0100, Greg Kroah-Hartman wrote:
> On Thu, Mar 14, 2024 at 07:02:46PM -0400, Kent Overstreet wrote:
> > On Thu, Mar 14, 2024 at 06:38:19PM -0400, Sasha Levin wrote:
> > > On Thu, Mar 14, 2024 at 05:46:35AM -0400, Kent Overstreet wrote:
> > > > On Thu, Mar 14, 2024 at 10:41:12AM +0100, Helge Deller wrote:
> > > > > Dear Greg & stable team,
> > > > > 
> > > > > could you please queue up the patch below for the stable-6.7 kernel?
> > > > > This is upstream commit:
> > > > > 	eba38cc7578bef94865341c73608bdf49193a51d
> > > > > 
> > > > > Thanks,
> > > > > Helge
> > > > 
> > > > I've already sent Greg a pull request with this patch - _twice_.
> > > 
> > > I'll point out, again, that if you read the docs it clearly points out
> > > that pull requests aren't a way to submit patches into stable.
> > 
> > Sasha, Greg and I already discussed and agreed that this would be the
> > plan for fs/bcachefs/.
> 
> I agreed?  I said that I would turn a pull request into individual
> patches, but that it's extra work for me to do so so that it usually
> will end up at the end of my work queue.  I'll get to this when I get
> back from vacation and catch up with other stuff in a few weeks, thanks.

No, you never said anything about turning a pull request into individual
patches; that was something I found out after you repeatedly mangled my
pull requests.

But how the pull requests get applied is entirely beside the point right
now, because apparently you agreed to a process without making any
provisions for having that continue while you were on vacation?

So now we've got a user data eating bug out there, with a fix that's
been sent to you, and you guys are just sitting on your hands.

You guys need to get your shit together - I've already let people know
that 6.7 is not safe to use and they need to immediately upgrade to 6.8,
but unfortunately not everyone will see that.

This is going to cause people reall pain.

      reply	other threads:[~2024-03-16  2:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-14  9:41 dddd Helge Deller
2024-03-14  9:46 ` dddd Kent Overstreet
2024-03-14 12:57   ` bachefs stable patches [was dddd] Helge Deller
2024-03-14 19:08     ` Kent Overstreet
2024-03-14 21:34       ` Helge Deller
2024-03-14 22:19         ` Kent Overstreet
2024-03-14 22:25           ` Helge Deller
2024-03-14 22:28             ` Kent Overstreet
2024-03-14 22:38   ` dddd Sasha Levin
2024-03-14 23:02     ` dddd Kent Overstreet
2024-03-15 18:27       ` dddd Greg Kroah-Hartman
2024-03-16  2:44         ` Kent Overstreet [this message]

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=v44t23xux6w4jrpcsh54z5r6ukya5afcgzmyczus4wkouszb5l@s2ofhjlwlz77 \
    --to=kent.overstreet@linux.dev \
    --cc=deller@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=sashal@kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).