linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Down <chris@chrisdown.name>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
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:08:04 +0100	[thread overview]
Message-ID: <YoZdVCfK4T8Ts2oS@chrisdown.name> (raw)
In-Reply-To: <YoZVvA5FP4wFLSH9@kroah.com>

Greg Kroah-Hartman writes:
>>  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.

Sorry, I'm getting more and more confused about what you're asking me to do, 
and less and less clear on the rationale.

Can you please clarify what "correctly cleaning up" would mean for a 
non-pointer `struct device'?

Is your concern that...

     register_console(c)
         device_initialize(c->d)
         device_add(c->d)
     unregister_console(c)
         device_unregister(c->d)      console_classdev_release(c->d)
     register_console(c)
         device_initialize(c->d)  <-- classdev was not previously zeroed out
				     in console_classdev_release() and bad 
				     things may happen

If that's not the point, I could really use some clarification about what 
"correctly cleaning up" means for a non-pointer `struct device' :-)

  reply	other threads:[~2022-05-19 15:08 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
2022-05-19 15:08               ` Chris Down [this message]
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=YoZdVCfK4T8Ts2oS@chrisdown.name \
    --to=chris@chrisdown.name \
    --cc=gregkh@linuxfoundation.org \
    --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;
as well as URLs for NNTP newsgroup(s).