linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krishanth Jagaduri <krishanth.jagaduri@sony.com>
To: John Ogness <john.ogness@linutronix.de>,
	Joseph Salisbury <joseph.salisbury@oracle.com>
Cc: Clark Williams <williams@redhat.com>,
	Petr Mladek <pmladek@suse.com>,
	Sergey Senozhatsky <senozhatsky@chromium.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Michael Thalmeier <michael.thalmeier@hale.at>,
	Vincent Whitchurch <vincent.whitchurch@axis.com>,
	Sebastian Siewior <bigeasy@linutronix.de>,
	linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org,
	Kento.A.Kobayashi@sony.com, Daniel.Palmer@sony.com
Subject: Re: [PATCH 5.15-rt] printk: ignore consoles without write() callback
Date: Wed, 23 Apr 2025 15:40:17 +0530	[thread overview]
Message-ID: <20250423-singing-bat-60c6f6@krishanthj> (raw)
In-Reply-To: <87zg9d99mp.fsf@jogness.linutronix.de>

On Thu, Feb 16, 2023 at 11:45:58AM +0106, John Ogness wrote:
> The ttynull driver does not provide an implementation for the write()
> callback. This leads to a NULL pointer dereference in the related
> printing kthread, which assumes it can call that callback.
> 
> Do not create kthreads for consoles that do not implement the write()
> callback. Also, for pr_flush(), ignore consoles that do not implement
> write() or write_atomic() since there is no way those consoles can
> flush their output.
> 
> ---
>  This is only a problem for the PREEMPT_RT tree. Mainline does not have
>  this problem.

Sorry for resurrecting this old thread but we actually want this patch
in 5.15-rt.

I am not sure why this was not applied to 5.15-rt yet since it is already
applied to 5.10-rt.

Could you please consider to pick this for 5.15-rt?

Best regards,
Krishanth

  parent reply	other threads:[~2025-04-23 10:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-16 10:39 [PATCH 5.15-rt] printk: ignore consoles without write() callback John Ogness
2023-02-16 16:54 ` Sebastian Siewior
2023-02-17  8:45   ` John Ogness
2023-02-17  8:47     ` [PATCH 5.10-rt] " John Ogness
2023-02-17 11:55       ` Luis Claudio R. Goncalves
2025-04-23 10:10 ` Krishanth Jagaduri [this message]
2025-04-28 14:45   ` [External] : Re: [PATCH 5.15-rt] " Joseph Salisbury
2025-05-21 12:30     ` Krishanth Jagaduri
2025-05-21 15:32       ` Joseph Salisbury
2025-05-23  5:05         ` Krishanth Jagaduri

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=20250423-singing-bat-60c6f6@krishanthj \
    --to=krishanth.jagaduri@sony.com \
    --cc=Daniel.Palmer@sony.com \
    --cc=Kento.A.Kobayashi@sony.com \
    --cc=bigeasy@linutronix.de \
    --cc=john.ogness@linutronix.de \
    --cc=joseph.salisbury@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=michael.thalmeier@hale.at \
    --cc=pmladek@suse.com \
    --cc=rostedt@goodmis.org \
    --cc=senozhatsky@chromium.org \
    --cc=vincent.whitchurch@axis.com \
    --cc=williams@redhat.com \
    /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).