From: Cong Wang <xiyou.wangcong@gmail.com>
To: Ranganath V N <vnranganath.20@gmail.com>
Cc: edumazet@google.com, davem@davemloft.net,
david.hunter.linux@gmail.com, horms@kernel.org, jhs@mojatatu.com,
jiri@resnulli.us, khalid@kernel.org, kuba@kernel.org,
pabeni@redhat.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, skhan@linuxfoundation.org,
syzbot+0c85cae3350b7d486aee@syzkaller.appspotmail.com
Subject: Re: [PATCH v4 net 0/2] net: sched: initialize struct tc_ife to fix kernel-infoleak
Date: Mon, 10 Nov 2025 12:02:15 -0800 [thread overview]
Message-ID: <aRJExzyyqdt1V6cP@pop-os.localdomain> (raw)
In-Reply-To: <20251109091336.9277-1-vnranganath.20@gmail.com>
On Sun, Nov 09, 2025 at 02:43:34PM +0530, Ranganath V N wrote:
> This series addresses the uninitialization of the struct which has
> 2 bytes of padding. And copying this uninitialized data to userspace
> can leak info from kernel memory.
>
> This series ensures all members and padding are cleared prior to
> begin copied.
>
> This change silences the KMSAN report and prevents potential information
> leaks from the kernel memory.
>
> Signed-off-by: Ranganath V N <vnranganath.20@gmail.com>
Looks good to me too.
Acked-by: Cong Wang <xiyou.wangcong@gmail.com>
Thanks!
next prev parent reply other threads:[~2025-11-10 20:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-09 9:13 [PATCH v4 net 0/2] net: sched: initialize struct tc_ife to fix kernel-infoleak Ranganath V N
2025-11-09 9:13 ` [PATCH net v4 1/2] net: sched: act_connmark: initialize struct tc_ife to fix kernel leak Ranganath V N
2025-11-09 9:30 ` Eric Dumazet
2025-11-09 9:13 ` [PATCH net v4 2/2] net: sched: act_ife: initialize struct tc_ife to fix KMSAN kernel-infoleak Ranganath V N
2025-11-09 9:31 ` Eric Dumazet
2025-12-12 0:54 ` Vitaly Chikunov
2025-12-12 16:26 ` Jamal Hadi Salim
2025-12-12 16:29 ` Jamal Hadi Salim
2025-12-14 21:38 ` Vitaly Chikunov
2025-12-15 16:27 ` Jamal Hadi Salim
2025-11-10 20:02 ` Cong Wang [this message]
2025-11-11 14:10 ` [PATCH v4 net 0/2] net: sched: initialize struct tc_ife to fix kernel-infoleak patchwork-bot+netdevbpf
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=aRJExzyyqdt1V6cP@pop-os.localdomain \
--to=xiyou.wangcong@gmail.com \
--cc=davem@davemloft.net \
--cc=david.hunter.linux@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=khalid@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=skhan@linuxfoundation.org \
--cc=syzbot+0c85cae3350b7d486aee@syzkaller.appspotmail.com \
--cc=vnranganath.20@gmail.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