From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Chris Down <chris@chrisdown.name>
Cc: linux-kernel@vger.kernel.org, Petr Mladek <pmladek@suse.com>,
kernel-team@fb.com
Subject: Re: [RFC PATCH] printk: console: Allow each console to have its own loglevel
Date: Thu, 19 May 2022 16:35:40 +0200 [thread overview]
Message-ID: <YoZVvA5FP4wFLSH9@kroah.com> (raw)
In-Reply-To: <YoZQQwtG12Ypr2IC@chrisdown.name>
On Thu, May 19, 2022 at 03:12:19PM +0100, Chris Down wrote:
> Greg Kroah-Hartman writes:
> > The two stanzas in my reply do NOT refer to the same thing.
> >
> > The first one is for the device that is assigned to the class. That
> > must be freed and properly reference counted and handled as that is a
> > dynamic object that can come and go as people add and remove consoles.
>
> Ah, I see. So to be clear, this change would fix what you're concerned
> about, right? :-)
>
> If so I'll do this in v2. Thanks!
>
> ---
>
> diff --git include/linux/console.h include/linux/console.h
> index ce5ba405285a..408dd86be8eb 100644
> --- include/linux/console.h
> +++ include/linux/console.h
> @@ -156,12 +156,6 @@ static inline int con_debug_leave(void)
> */
> #define CON_LOGLEVEL (128) /* Level set locally for this console */
> -/*
> - * Console has active class device, so may have active readers/writers from
> - * /sys/class hierarchy.
> - */
> -#define CON_CLASSDEV_ACTIVE (256)
> -
> struct console {
> char name[16];
> void (*write)(struct console *, const char *, unsigned);
> @@ -179,9 +173,11 @@ struct console {
> void *data;
> struct console *next;
> int level;
> - struct device classdev;
> + struct device *classdev;
Ick, no, keep the real structure here. It can properly handle the
reference counting for the object. Just correctly clean up in the
release function, not anywhere else.
thanks,
greg k-h
next prev parent reply other threads:[~2022-05-19 14:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 14:24 [RFC PATCH] printk: console: Allow each console to have its own loglevel Chris Down
2022-05-18 14:32 ` Chris Down
2022-05-18 15:34 ` Greg Kroah-Hartman
2022-05-18 19:46 ` Chris Down
2022-05-18 19:54 ` Greg Kroah-Hartman
2022-05-18 20:27 ` Chris Down
2022-05-19 7:04 ` Greg Kroah-Hartman
2022-05-19 14:12 ` Chris Down
2022-05-19 14:35 ` Greg Kroah-Hartman [this message]
2022-05-19 15:08 ` Chris Down
2022-05-19 15:24 ` Greg Kroah-Hartman
2022-05-19 15:25 ` Greg Kroah-Hartman
2022-05-19 15:55 ` Chris Down
2022-05-19 17:45 ` Greg Kroah-Hartman
2022-05-19 17:55 ` Chris Down
2022-05-24 9:19 ` Petr Mladek
2022-05-30 10:48 ` [OFFLIST] " Chris Down
2022-05-30 10:49 ` Chris Down
2022-05-19 7:26 ` Geert Uytterhoeven
2022-05-19 14:37 ` Chris Down
2022-05-19 17:48 ` Geert Uytterhoeven
2022-05-19 18:05 ` Chris Down
2022-05-19 13:59 ` [printk] 6f922c8d53: BUG:kernel_NULL_pointer_dereference,address kernel test robot
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=YoZVvA5FP4wFLSH9@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=chris@chrisdown.name \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.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