From: Paolo Abeni <pabeni@redhat.com>
To: "Kriish Sharma" <kriish.sharma2006@gmail.com>,
"Krzysztof Hałasa" <khalasa@piap.pl>
Cc: khc@pm.waw.pl, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers/net/wan/hdlc_ppp: fix potential null pointer in ppp_cp_event logging
Date: Tue, 7 Oct 2025 10:41:45 +0200 [thread overview]
Message-ID: <d8fb2384-66bb-473a-a020-1bd816b5766c@redhat.com> (raw)
In-Reply-To: <CAL4kbROGfCnLhYLCptND6Ni2PGJfgZzM+2kjtBhVcvy3jLHtfQ@mail.gmail.com>
On 10/3/25 8:43 AM, Kriish Sharma wrote:
> Thanks for the clarification.
> I can update proto_name() to return "LCP" by default instead of NULL,
> which should silence the compiler without changing behavior.
> I can send another patch for this if you'd like.
If v2 is not ready yet, I think it would be better returning "unknown"
instead of "LCP" when the protocol id is actually unknown.
In the current code base, such case is unexpected/impossible, but the
compiler force us to handle it anyway. I think we should avoid hiding
the unexpected event.
Assuming all the code paths calling proto_name() ensure the pid is a
valid one, you should possibly add a WARN_ONCE() on the default case.
Thanks,
Paolo
next prev parent reply other threads:[~2025-10-07 8:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 18:05 Kriish Sharma
2025-10-02 18:16 ` Dimitri Daskalakis
2025-10-02 18:31 ` Kriish Sharma
2025-10-03 6:34 ` Krzysztof Hałasa
2025-10-03 6:43 ` Kriish Sharma
2025-10-07 8:41 ` Paolo Abeni [this message]
2025-10-07 9:28 ` Krzysztof Hałasa
2025-10-07 10:46 ` Paolo Abeni
2025-10-07 11:38 ` Krzysztof Hałasa
2025-10-03 8:33 ` Simon Horman
2025-10-03 9:02 ` Kriish Sharma
2025-10-03 9:40 ` Simon Horman
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=d8fb2384-66bb-473a-a020-1bd816b5766c@redhat.com \
--to=pabeni@redhat.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=khalasa@piap.pl \
--cc=khc@pm.waw.pl \
--cc=kriish.sharma2006@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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®