From: Simon Horman <horms@kernel.org>
To: Charalampos Mitrodimas <charmitro@posteo.net>
Cc: Steffen Klassert <steffen.klassert@secunet.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
David Ahern <dsahern@kernel.org>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
syzbot+01b0667934cdceb4451c@syzkaller.appspotmail.com
Subject: Re: [PATCH net v2] net: ipv6: fix buffer overflow in AH output
Date: Mon, 28 Jul 2025 14:50:55 +0100 [thread overview]
Message-ID: <20250728135055.GA1877762@horms.kernel.org> (raw)
In-Reply-To: <871pq05w74.fsf@posteo.net>
On Mon, Jul 28, 2025 at 12:36:18PM +0000, Charalampos Mitrodimas wrote:
> Simon Horman <horms@kernel.org> writes:
>
> > On Sun, Jul 27, 2025 at 09:51:40PM +0000, Charalampos Mitrodimas wrote:
...
> >> Changes in v2:
> >> - Link correct syzbot dashboard link in patch tags
> >> - Link to v1: https://lore.kernel.org/r/20250727-ah6-buffer-overflow-v1-1-1f3e11fa98db@posteo.net
> >
> > You posted two versions of this patch within a few minutes.
> > Please don't do that. Rather, please wait 24h to allow review to occur.
>
> I'm aware. The reason for posting the second version so soon was because
> I did not want people to get confused about which syzbot report this
> solves, as the one in v1 was the wrong.
Understood. FWIIW, I think it would have been better
to respond to v1 with corrected syzbot information.
...
> This is much better actually, thanks a lot. I tested it with the syzbot
> reproducer and no issues were found.
Excellent.
> > I would also suggest adding a helper (or two), to avoid (repeatedly) open
> > coding whatever approach is taken.
>
> I'll do that and go on with a patch targetting ipsec-next. Is it okay to
> keep the the versioning or it should a completely new patch?
I think that keeping the versioning is fine, although it is up to you.
If you do so, please do include a link to earlier versions
(as you did in this patch) as I assume the subject will change.
--
pw-bot: cr
prev parent reply other threads:[~2025-07-28 13:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-27 21:51 Charalampos Mitrodimas
2025-07-28 11:36 ` Simon Horman
2025-07-28 12:36 ` Charalampos Mitrodimas
2025-07-28 13:50 ` Simon Horman [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=20250728135055.GA1877762@horms.kernel.org \
--to=horms@kernel.org \
--cc=charmitro@posteo.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=steffen.klassert@secunet.com \
--cc=syzbot+01b0667934cdceb4451c@syzkaller.appspotmail.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
all inboxes | Powered by JetHome®