mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Maxime Chevallier <maxime.chevallier@bootlin.com>
To: Aleksei Sviridkin <f@lex.la>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] net: phy: reject attach while the PHY driver is in transition
Date: Thu, 17 Sep 2026 22:30:43 +0200	[thread overview]
Message-ID: <65b2eff4-6818-4cfa-a0e7-d48729e0cd9e@bootlin.com> (raw)
In-Reply-To: <20260917183345.37604-1-f@lex.la>

Hi,

On 9/17/26 20:33, Aleksei Sviridkin wrote:
> Fine, v2 will target net-next.
> 
> Out of curiosity, since I will run into this again: is the line
> "needs instrumentation to reproduce -> net-next" about the window
> being unreachable in practice, or about nobody having reported it?

Well there are lots of patches recently that fix bugs that are never
seen, and only show-up if some oddball error path is taken, under
conditions almost impossible to encounter in real life or even
reproduce without instrumenting the code to force these conditions.

> The crash itself came from a real board; the msleep() only made the
> race deterministic instead of occasional.

This is something you should say in the commit log then, it's important
to know this was seen in real life. If that's the case, then yes it's
'net' material instead of 'net-next'.

Maxime

  reply	other threads:[~2026-09-17 20:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-14 20:42 Aleksei Sviridkin
2026-09-17 11:43 ` netdev-bot+sashiko
2026-09-17 12:00 ` Maxime Chevallier
2026-09-17 18:33   ` Aleksei Sviridkin
2026-09-17 20:30     ` Maxime Chevallier [this message]
2026-09-17 21:04       ` Aleksei Sviridkin

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=65b2eff4-6818-4cfa-a0e7-d48729e0cd9e@bootlin.com \
    --to=maxime.chevallier@bootlin.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=f@lex.la \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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

all inboxes | Powered by JetHome®