From: Jakub Kicinski <kuba@kernel.org>
To: Jiayuan Chen <jiayuan.chen@linux.dev>
Cc: horms@kernel.org, bpf@vger.kernel.org, netdev@vger.kernel.org,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, ricardo@marliere.net, viro@zeniv.linux.org.uk,
dmantipov@yandex.ru, aleksander.lobakin@intel.com,
linux-ppp@vger.kernel.org, linux-kernel@vger.kernel.org,
mrpre@163.com,
syzbot+853242d9c9917165d791@syzkaller.appspotmail.com
Subject: Re: [PATCH net-next v4 1/1] ppp: Fix KMSAN warning by initializing 2-byte header
Date: Fri, 28 Feb 2025 14:02:02 -0800 [thread overview]
Message-ID: <20250228140202.7f39a30c@kernel.org> (raw)
In-Reply-To: <wm7gi3hafgaruhnjaz5bqdv7yrduf6cum3gljylypzqkvw2ctw@b2zb75i2hpid>
On Fri, 28 Feb 2025 12:55:41 +0800 Jiayuan Chen wrote:
> > The exact same problem seems to be present in ppp_receive_nonmp_frame()
> > please fix them both.
> > --
> > pw-bot: cr
> Thanks, Jakub! I'll do that.
>
> I was previously worried that the commit message would be too long,
> so I put the detailed information in the cover letter instead. I'll make
> the commit message more concise.
FWIW we commit the cover letter as well, as a merge commit.
So both would end up in the tree.
prev parent reply other threads:[~2025-02-28 22:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 1:36 [PATCH net-next v4 0/1] ppp: Fix KMSAN uninit-value warning with bpf Jiayuan Chen
2025-02-26 1:36 ` [PATCH net-next v4 1/1] ppp: Fix KMSAN warning by initializing 2-byte header Jiayuan Chen
2025-02-28 1:48 ` Jakub Kicinski
2025-02-28 4:55 ` Jiayuan Chen
2025-02-28 22:02 ` Jakub Kicinski [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=20250228140202.7f39a30c@kernel.org \
--to=kuba@kernel.org \
--cc=aleksander.lobakin@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=dmantipov@yandex.ru \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jiayuan.chen@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ppp@vger.kernel.org \
--cc=mrpre@163.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ricardo@marliere.net \
--cc=syzbot+853242d9c9917165d791@syzkaller.appspotmail.com \
--cc=viro@zeniv.linux.org.uk \
/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 NNTP newsgroup(s).