linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: Manuel Fombuena <fombuena@outlook.com>
Cc: pavel@ucw.cz, corbet@lwn.net, linux-leds@vger.kernel.org,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND 1/5] leds: leds-st1202: fix NULL pointer access on race condition
Date: Thu, 13 Feb 2025 10:24:49 +0000	[thread overview]
Message-ID: <20250213102449.GC2756671@google.com> (raw)
In-Reply-To: <CWLP123MB547308A731A2B7F1B7FF12DFC5FC2@CWLP123MB5473.GBRP123.PROD.OUTLOOK.COM>

On Wed, 12 Feb 2025, Manuel Fombuena wrote:

> On Tue, 11 Feb 2025, Lee Jones wrote:
> 
> > On Sat, 01 Feb 2025, Manuel Fombuena wrote:
> > 
> > > st1202_dt_init() calls devm_led_classdev_register_ext() before the
> > > internal data structures are properly setup, so the leds become visible
> > > to user space while being partially initialized, leading to a window
> > > where trying to access them causes a NULL pointer access.
> > 
> > If this is true, you need to provide a Fixes: tag and to Cc: Stable.
> >
> > Documentation/process/stable-kernel-rules.rst
> > 
> 
> Yes, some circumstances have to confluence but it is reproducible under 
> normal use. I can send panic logs if you want to see the details.
> 
> Since this driver has been added in 6.14-rc1, I thought that, if applied,    
> this patch would be included in fixes before the final release and there 
> would be no need to apply it to -stable trees, as it is nowhere else at 
> the moment. But of course I will review the documentation and make changes as 
> suggested.

Then you need to separate the set into patches you expect to be
submitted to the -rcs and ones which can be applied during the next
cycle, then go to lengths to explain that either in the diff section of
each patch (preferred) or in the cover-letter.

Either way, you need Fixes: tags.

-- 
Lee Jones [李琼斯]

  reply	other threads:[~2025-02-13 10:24 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-01 13:00 [PATCH RESEND 0/5] LED1202 / leds-st1202 fixes and improvements Manuel Fombuena
2025-02-01 13:02 ` [PATCH RESEND 1/5] leds: leds-st1202: fix NULL pointer access on race condition Manuel Fombuena
2025-02-11 13:31   ` Lee Jones
2025-02-12 16:28     ` Manuel Fombuena
2025-02-13 10:24       ` Lee Jones [this message]
2025-02-13 15:25         ` Manuel Fombuena
2025-02-20 15:01           ` Lee Jones
2025-02-11 13:34   ` Lee Jones
2025-02-12 13:16     ` Manuel Fombuena
2025-02-01 13:04 ` [PATCH RESEND 2/5] leds: leds-st1202: initialize hardware before DT node child operations Manuel Fombuena
2025-02-11 13:32   ` Lee Jones
2025-02-12 15:15     ` Manuel Fombuena
2025-02-01 13:04 ` [PATCH RESEND 3/5] leds: leds-st1202: spacing and proofreading editing Manuel Fombuena
2025-02-11 13:34   ` Lee Jones
2025-02-12 14:28     ` Manuel Fombuena
2025-02-01 13:05 ` [PATCH RESEND 4/5] leds: Kconfig: leds-st1202: add select for required LEDS_TRIGGER_PATTERN Manuel Fombuena
2025-02-01 13:07 ` [PATCH RESEND 5/5] Documentation: leds: remove .rst extension for leds-st1202 on index Manuel Fombuena
2025-02-13 10:41 ` [PATCH RESEND 0/5] LED1202 / leds-st1202 fixes and improvements Lee Jones
2025-02-13 15:54   ` Manuel Fombuena
2025-02-20 15:03     ` Lee Jones

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=20250213102449.GC2756671@google.com \
    --to=lee@kernel.org \
    --cc=corbet@lwn.net \
    --cc=fombuena@outlook.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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).