From: "Cen Zhang (Microsoft Security FORGE Labs)" <cenzhang@linux.microsoft.com>
To: xuanqiang.luo@linux.dev
Cc: AutonomousCodeSecurity@microsoft.com, ameryhung@gmail.com,
ast@kernel.org, bestswngs@gmail.com, bpf@vger.kernel.org,
daniel@iogearbox.net, davem@davemloft.net, edumazet@google.com,
horms@kernel.org, kees@kernel.org, kuba@kernel.org,
kys@microsoft.com, linux-kernel@vger.kernel.org,
martin.lau@kernel.org, mattbobrowski@google.com,
menglong8.dong@gmail.com, netdev@vger.kernel.org,
pabeni@redhat.com, tgopinath@linux.microsoft.com,
wangfushuai@baidu.com, xmei5@asu.edu
Subject: Re: [PATCH bpf] bpf: Fix NULL pointer dereference in __bpf_sk_storage_map_seq_show
Date: Fri, 11 Sep 2026 09:57:36 -0400 [thread overview]
Message-ID: <20260911135736.80463-1-cenzhang@linux.microsoft.com> (raw)
In-Reply-To: <c3f2a61d-d5bc-454c-987d-717b5f8c8809@linux.dev>
Hi Amery and Xuanqiang,
Sorry for the delayed response. I somehow missed this thread.
For clarity, I am using my new Microsoft-approved email address,
cenzhang@linux.microsoft.com, for this reply and v2.
Thanks for all the reviews. I'll send v2 shortly with SEQ_SKIP as the
return value and the suggested Fixes tag.
Thanks,
Cen
prev parent reply other threads:[~2026-09-11 13:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-27 5:18 [PATCH bpf] bpf: Fix NULL pointer dereference in __bpf_sk_storage_map_seq_show Cen Zhang (Microsoft Security FORGE Labs)
2026-08-27 5:38 ` sashiko-bot
2026-08-27 10:33 ` Amery Hung
2026-08-27 5:49 ` bot+bpf-ci
2026-08-27 10:41 ` Amery Hung
2026-09-11 7:45 ` Xuanqiang Luo
2026-09-11 13:57 ` Cen Zhang (Microsoft Security FORGE Labs) [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=20260911135736.80463-1-cenzhang@linux.microsoft.com \
--to=cenzhang@linux.microsoft.com \
--cc=AutonomousCodeSecurity@microsoft.com \
--cc=ameryhung@gmail.com \
--cc=ast@kernel.org \
--cc=bestswngs@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kees@kernel.org \
--cc=kuba@kernel.org \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@kernel.org \
--cc=mattbobrowski@google.com \
--cc=menglong8.dong@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tgopinath@linux.microsoft.com \
--cc=wangfushuai@baidu.com \
--cc=xmei5@asu.edu \
--cc=xuanqiang.luo@linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.