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 17:24:29 +0200 [thread overview]
Message-ID: <YoZhLTm3Rwi4pve4@kroah.com> (raw)
In-Reply-To: <YoZdVCfK4T8Ts2oS@chrisdown.name>
On Thu, May 19, 2022 at 04:08:04PM +0100, Chris Down wrote:
> 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' :-)
The problem is that your release() callback for your class HAS TO clean
up the memory for that object. You can not have an empty function, or
just say "it will be handled elsewhere." That is the LAST call that
will be made when the object is to be freed from memory, as that is when
the last reference count is dropped. Anytime before then, you do not
know if it is safe to free the memory or not.
Does that help?
thanks,
greg k-h
next prev parent reply other threads:[~2022-05-19 15:26 UTC|newest]
Thread overview: 25+ 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
2022-05-19 15:24 ` Greg Kroah-Hartman [this message]
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 4:48 ` kernel test robot
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
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=YoZhLTm3Rwi4pve4@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.