From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Alan Stern <stern@rowland.harvard.edu>, linux-usb@vger.kernel.org
Cc: "Joe Perches" <joe@perches.com>,
"Daniel Drake" <drake@endlessm.com>,
"Dmitry Fleytman" <dmitry@daynix.com>,
"Eugene Korenevsky" <ekorenevsky@gmail.com>,
"Geert Uytterhoeven" <geert@linux-m68k.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Günter Röck" <linux@roeck-us.net>,
"Johan Hovold" <johan@kernel.org>,
"Mathias Nyman" <mathias.nyman@linux.intel.com>,
"Peter Chen" <peter.chen@nxp.com>,
LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org
Subject: Re: USB: hub: Delete an error message for a failed memory allocation in usb_hub_clear_tt_buffer()
Date: Wed, 06 Dec 2017 21:33:26 +0000 [thread overview]
Message-ID: <a823c472-7826-3fbd-0197-5246a2cd5368@users.sourceforge.net> (raw)
In-Reply-To: <97b0eeb8-834e-61ca-01dd-afbbf18697db@users.sourceforge.net>
>>> Does the existing memory allocation error message include the
>>> &udev->dev device name and driver name? If it doesn't, there will be
>>> no way for the user to tell that the error message is related to the
>>> device failure.
>>
>> No, but the effect is similar.
>>
>> OOM does a dump_stack() so this function's call tree is shown.
>
> A call stack doesn't tell you which device was being handled.
Do you find a default Linux allocation failure report insufficient then?
Would you like to to achieve that the requested information can be determined
from a backtrace?
Regards,
Markus
next prev parent reply other threads:[~2017-12-06 21:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-06 17:51 USB: hub: Delete an error message for a failed memory allocation in usb_hub_clear_tt_buffer() SF Markus Elfring
2017-12-06 20:20 ` Geert Uytterhoeven
2017-12-06 21:33 ` SF Markus Elfring [this message]
2017-12-06 22:02 ` Alan Stern
2017-12-07 7:40 ` Geert Uytterhoeven
2017-12-07 8:35 ` Dan Carpenter
2017-12-07 8:45 ` Geert Uytterhoeven
2017-12-07 8:56 ` Greg Kroah-Hartman
2017-12-07 9:17 ` Oliver Neukum
2017-12-07 9:30 ` Dan Carpenter
2017-12-07 13:38 ` SF Markus Elfring
2017-12-07 15:12 ` Alan Stern
2017-12-07 16:20 ` Joe Perches
2017-12-07 20:51 ` Dan Carpenter
2017-12-07 21:26 ` Alan Stern
2017-12-08 7:43 ` Geert Uytterhoeven
2017-12-08 11:11 ` Dan Carpenter
2017-12-08 17:42 ` Alan Stern
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=a823c472-7826-3fbd-0197-5246a2cd5368@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=dmitry@daynix.com \
--cc=drake@endlessm.com \
--cc=ekorenevsky@gmail.com \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=johan@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mathias.nyman@linux.intel.com \
--cc=peter.chen@nxp.com \
--cc=stern@rowland.harvard.edu \
/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