From: Tom Rini <trini@konsulko.com>
To: Joe Hershberger <joe.hershberger@ni.com>,
Ramon Fried <rfried.dev@gmail.com>,
MD Danish Anwar <danishanwar@ti.com>,
Jai Luthra <j-luthra@ti.com>,
Siddharth Vadapalli <s-vadapalli@ti.com>,
Nishanth Menon <nm@ti.com>, Udit Kumar <u-kumar1@ti.com>,
Suman Anna <s-anna@ti.com>,
Matthias Schiffer <matthias.schiffer@ew.tq-group.com>
Cc: u-boot@lists.denx.de, u-boot@ew.tq-group.com
Subject: Re: [PATCH 1/5] net: eth-uclass: guard against reentrant eth_init()/eth_halt() calls
Date: Wed, 15 May 2024 17:28:55 -0600 [thread overview]
Message-ID: <171581573568.812585.13429362076523742879.b4-ty@konsulko.com> (raw)
In-Reply-To: <de7fe2da7ae4a85252d63904fae61585e4641936.1714117337.git.matthias.schiffer@ew.tq-group.com>
On Fri, 26 Apr 2024 10:02:24 +0200, Matthias Schiffer wrote:
> With netconsole, any log message can result in an eth_init(), possibly
> causing an reentrant call into eth_init() if a driver's ops print
> anything:
>
> eth_init() -> driver.start() -> printf() -> netconsole -> eth_init()
> eth_halt() -> driver.stop() -> printf() -> netconsole -> eth_init()
>
> [...]
Applied to u-boot/next, thanks!
--
Tom
prev parent reply other threads:[~2024-05-15 23:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 8:02 [PATCH 1/5] net: eth-uclass: guard against reentrant eth_init()/eth_halt() calls Matthias Schiffer
2024-04-26 8:02 ` [PATCH 2/5] net: ti: am65-cpsw-nuss: avoid errors due to imbalanced start()/stop() Matthias Schiffer
2024-04-26 8:02 ` [PATCH 3/5] net: ti: am65-cpsw-nuss: fix error handling for "RX dma add buf failed" Matthias Schiffer
2024-04-26 8:02 ` [PATCH 4/5] dma: ti: k3-udma: add missing <net.h> include Matthias Schiffer
2024-04-26 8:02 ` [PATCH 5/5] dma: ti: k3-udma: invalidate prepared buffers before pushing to recv ring Matthias Schiffer
2024-05-03 18:42 ` Sverdlin, Alexander
2024-04-26 8:09 ` [PATCH 1/5] net: eth-uclass: guard against reentrant eth_init()/eth_halt() calls Siddharth Vadapalli
2024-05-15 23:28 ` Tom Rini [this message]
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=171581573568.812585.13429362076523742879.b4-ty@konsulko.com \
--to=trini@konsulko.com \
--cc=danishanwar@ti.com \
--cc=j-luthra@ti.com \
--cc=joe.hershberger@ni.com \
--cc=matthias.schiffer@ew.tq-group.com \
--cc=nm@ti.com \
--cc=rfried.dev@gmail.com \
--cc=s-anna@ti.com \
--cc=s-vadapalli@ti.com \
--cc=u-boot@ew.tq-group.com \
--cc=u-boot@lists.denx.de \
--cc=u-kumar1@ti.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 read-only IMAP folder(s) and NNTP newsgroup(s).