From: Jakub Kicinski <kuba@kernel.org>
To: Simon Horman <horms@kernel.org>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Jon Maloy <jmaloy@redhat.com>,
Ying Xue <ying.xue@windriver.com>,
Per Liden <per.liden@nospam.ericsson.com>,
netdev@vger.kernel.org, tipc-discussion@lists.sourceforge.net
Subject: Re: [PATCH net-next] tipic: guard against buffer overrun in bearer_name_validate()
Date: Wed, 31 Jul 2024 18:23:56 -0700 [thread overview]
Message-ID: <20240731182356.01a4c2b8@kernel.org> (raw)
In-Reply-To: <20240731-tipic-overrun-v1-1-32ce5098c3e9@kernel.org>
On Wed, 31 Jul 2024 09:11:50 +0100 Simon Horman wrote:
> Subject: [PATCH net-next] tipic: guard against buffer overrun in bearer_name_validate()
double space and one too many 'i's in the subject
Code looks right:
Reviewed-by: Jakub Kicinski <kuba@kernel.org>
--
pw-bot: cr
prev parent reply other threads:[~2024-08-01 1:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 8:11 [PATCH net-next] tipic: guard against buffer overrun in bearer_name_validate() Simon Horman
2024-08-01 1:23 ` 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=20240731182356.01a4c2b8@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jmaloy@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=per.liden@nospam.ericsson.com \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=ying.xue@windriver.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 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.