public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Matthew Brost <matthew.brost@intel.com>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
	Tejun Heo <tj@kernel.org>, Lai Jiangshan <jiangshanlai@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] workqueue: fix null-ptr-deref on __alloc_workqueue() error
Date: Wed, 21 Aug 2024 09:07:22 +0900	[thread overview]
Message-ID: <20240821000722.GG12106@google.com> (raw)
In-Reply-To: <ZsUtOnyDVJJ96bXZ@DUT025-TGLU.fm.intel.com>

On (24/08/20 23:56), Matthew Brost wrote:
> On Wed, Aug 21, 2024 at 08:54:12AM +0900, Sergey Senozhatsky wrote:
> > On (24/08/19 11:15), Tejun Heo wrote:
> > > Hello,
> > > 
> > > On Fri, Aug 16, 2024 at 02:45:20AM +0000, Matthew Brost wrote:
> > > > > Tejun, how do you plan to handle this?  Would it be possible to
> > > > > drop current series from your tree so that Matthew can send an
> > > > > updated version (with all the fixes squashed)?
> > > > 
> > > > Tejun, yes let me know how to move forward with this as it is highly
> > > > desired for Intel Xe team to get this into 6.12.
> > > 
> > > Can you just send a fixup patch?
> > 
> > Well, this will make the tree unbisectable (for a range of versions),
> > because the errors in question break the boot.
> 
> Can the patches not just get squashed together in the 6.12 PR?

squash would be my personal preference.  Usually resend works in cases
like this (so that Link: in commit messages point to the relevant
thread), but I don't know what Tejun's planning to do.

  reply	other threads:[~2024-08-21  0:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-15  7:02 [PATCH] workqueue: fix null-ptr-deref on __alloc_workqueue() error Sergey Senozhatsky
2024-08-15  7:09 ` Sergey Senozhatsky
2024-08-15  7:24   ` Sergey Senozhatsky
2024-08-15 15:56     ` Matthew Brost
2024-08-15 16:24       ` Matthew Brost
2024-08-16  2:38         ` Sergey Senozhatsky
2024-08-16  2:45           ` Matthew Brost
2024-08-16  2:52             ` Sergey Senozhatsky
2024-08-19 21:15             ` Tejun Heo
2024-08-19 23:57               ` Matthew Brost
2024-08-20 23:54               ` Sergey Senozhatsky
2024-08-20 23:56                 ` Matthew Brost
2024-08-21  0:07                   ` Sergey Senozhatsky [this message]
2024-08-21  0:04                 ` Tejun Heo
2024-08-21  0:09                   ` Sergey Senozhatsky
2024-08-21 16:14 ` Tejun Heo

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=20240821000722.GG12106@google.com \
    --to=senozhatsky@chromium.org \
    --cc=jiangshanlai@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew.brost@intel.com \
    --cc=tj@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