From: Jakub Kicinski <kuba@kernel.org>
To: HighW4y2H3ll <huzh@nyu.edu>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] Fix buffer overflow in hinic_devlink.c:hinic_flash_fw
Date: Fri, 17 Jun 2022 20:01:30 -0700 [thread overview]
Message-ID: <20220617200130.7ef96a66@kernel.org> (raw)
In-Reply-To: <20220617050101.37620-1-huzh@nyu.edu>
On Fri, 17 Jun 2022 01:01:02 -0400 HighW4y2H3ll wrote:
> Subject: [PATCH v2] Fix buffer overflow in hinic_devlink.c:hinic_flash_fw
> Date: Fri, 17 Jun 2022 01:01:02 -0400
> X-Mailer: git-send-email 2.35.1
>
> Signed-off-by: zhenghao hu <huzh@nyu.edu>
Please describe in the commit message what the buffer overflow is, so
we don't have to reverse engineer your change.
Also please add a Fixes tag pointing at a commit which introduced the
bug.
next prev parent reply other threads:[~2022-06-18 3:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 5:01 [PATCH v2] Fix buffer overflow in hinic_devlink.c:hinic_flash_fw HighW4y2H3ll
2022-06-18 3:01 ` Jakub Kicinski [this message]
2022-06-27 16:15 ` kernel test robot
2022-06-27 17:19 ` Zhenghao Hu
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=20220617200130.7ef96a66@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=huzh@nyu.edu \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).