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: Fri, 16 Aug 2024 11:52:23 +0900	[thread overview]
Message-ID: <20240816025223.GE12106@google.com> (raw)
In-Reply-To: <Zr69QOysEfYXkMwb@DUT025-TGLU.fm.intel.com>

On (24/08/16 02:45), Matthew Brost wrote:
[..]
> > Oh, I haven't checked the workqueue header.  Yes, you are right.
> > A macro should work.
> > 
> 
> To be clear we your change to __alloc_workqueue in workqueue.c AND my
> change to a macro in workqueue.h.

Oh, yes, correct, that's what I meant too - we need both.

// Plus a null-ptr-deref fix in __alloc_workqueue() error path.

  reply	other threads:[~2024-08-16  2:52 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 [this message]
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
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=20240816025223.GE12106@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