From: Greg KH <gregkh@linuxfoundation.org>
To: Xu Yang <xu.yang_2@nxp.com>
Cc: benjamin.tissoires@redhat.com, hdegoede@redhat.com,
ivan.orlov0322@gmail.com, heikki.krogerus@linux.intel.com,
linux-usb@vger.kernel.org, linux-imx@nxp.com, jun.li@nxp.com
Subject: Re: [PATCH] usb: roles: try to get/put all relevant modules
Date: Fri, 12 Jan 2024 09:26:54 +0100 [thread overview]
Message-ID: <2024011220-asleep-dragster-1e39@gregkh> (raw)
In-Reply-To: <2024011213-situated-augmented-64a4@gregkh>
On Fri, Jan 12, 2024 at 09:24:11AM +0100, Greg KH wrote:
> On Fri, Jan 12, 2024 at 04:01:08PM +0800, Xu Yang wrote:
> > +void usb_role_switch_get_modules(struct device *dev)
> > +{
> > + while (dev) {
> > + if (dev->driver)
> > + WARN_ON(!try_module_get(dev->driver->owner));
>
> You just crashed all systems that have panic-on-warn enabled, which is
> by far (i.e. in the billions) the huge majority of Linux systems in the
> world.
>
> If this is something that can fail, then properly handle the issue,
> don't just give up and say "let's fill the kernel log with a mess and
> reboot the box!".
Ah, I see now you are just moving the code, but please, let's fix this
properly, don't persist in the wrong code here.
thanks,
greg k-h
next prev parent reply other threads:[~2024-01-12 8:26 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-12 8:01 [PATCH] usb: roles: try to get/put all relevant modules Xu Yang
2024-01-12 8:24 ` Greg KH
2024-01-12 8:26 ` Greg KH [this message]
2024-01-12 9:28 ` [EXT] " Xu Yang
2024-01-12 13:52 ` Greg KH
2024-01-15 3:02 ` Xu Yang
2024-01-15 6:54 ` Greg KH
2024-01-15 16:31 ` Alan Stern
2024-01-16 5:44 ` Xu Yang
2024-01-16 16:03 ` Alan Stern
2024-01-17 5:57 ` Xu Yang
2024-01-18 9:22 ` Heikki Krogerus
2024-01-18 9:53 ` Greg KH
2024-01-18 12:38 ` Heikki Krogerus
2024-01-18 14:54 ` Greg KH
2024-01-18 15:28 ` Alan Stern
2024-01-18 15:52 ` Xu Yang
2024-01-18 19:21 ` Alan Stern
2024-01-19 8:18 ` Xu Yang
2024-01-19 13:21 ` Heikki Krogerus
2024-01-19 14:53 ` Alan Stern
2024-01-19 11:13 ` Xu Yang
2024-01-19 15:00 ` Alan Stern
2024-01-19 15:23 ` Xu Yang
2024-01-19 16:22 ` Alan Stern
2024-01-22 2:32 ` Xu Yang
2024-01-18 15:29 ` Xu Yang
2024-01-14 12:25 ` Greg KH
2024-01-14 23:06 ` kernel test robot
2024-01-15 2:12 ` 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=2024011220-asleep-dragster-1e39@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=benjamin.tissoires@redhat.com \
--cc=hdegoede@redhat.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=ivan.orlov0322@gmail.com \
--cc=jun.li@nxp.com \
--cc=linux-imx@nxp.com \
--cc=linux-usb@vger.kernel.org \
--cc=xu.yang_2@nxp.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