mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Новиков Артём" <naa@amicon.ru>
To: "netdev-bot+sinfo@kernel.org" <netdev-bot+sinfo@kernel.org>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Sasha Levin" <sashal@kernel.org>,
	"lvc-project@linuxtesting.org" <lvc-project@linuxtesting.org>,
	"Разов Роман" <rrv@amicon.ru>,
	"pchelkin@ispras.ru" <pchelkin@ispras.ru>,
	"David S. Miller" <davem@davemloft.net>,
	"Jakub Kicinski" <kuba@kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 5.10] vxlan: Fix potential null-ptr-deref in vxlan_gro_prepare_receive().
Date: Thu, 1 Oct 2026 14:35:01 +0000	[thread overview]
Message-ID: <62ee20aae4004f87b03a0e618572a1c8@amicon.ru> (raw)
In-Reply-To: <179086101460.31693.11225223420004934540@kernel.org>

Hi,

Resending in plain text because the mailing lists rejected the
HTML version of my previous reply.

This is a stable backport of Kuniyuki Iwashima's upstream commit
30a45c0bffdd62350261e2f2689fdba426a33578.

The original upstream submission does not specify how the issue
was discovered. I don't have additional information about the
original discovery method.

The backport adapts the NULL check to the older vxlan_gro_receive()
implementation in 5.10. The adaptation is described above my
Signed-off-by.

Best regards,
Artem Novikov

От: netdev-bot+sinfo@kernel.org <netdev-bot+sinfo@kernel.org>
Отправлено: 1 октября 2026 г. 16:23
Кому: Новиков Артём
Копия: stable@vger.kernel.org; Greg Kroah-Hartman; Sasha Levin; lvc-project@linuxtesting.org; Разов Роман; pchelkin@ispras.ru; David S. Miller; Jakub Kicinski; netdev@vger.kernel.org; linux-kernel@vger.kernel.org
Тема: Re: [PATCH 5.10] vxlan: Fix potential null-ptr-deref in vxlan_gro_prepare_receive().
    
Hi!

This is an automated message. This series looks like a fix, but its
commit messages seem to be missing some information:

 - How the issue was discovered, e.g. hit in production, hit during
   development, syzbot report, manual code inspection, LLM or static
   analysis tool scan.

Please do not repost the series just to address the above. Instead,
reply to this email with the missing information, so that reviewers
can take it into account. If the series needs another revision for
other reasons, please include the information in the commit messages
then.

The evaluation is done by an LLM so it may be wrong, if you think
that is the case please reply and explain.
    

      reply	other threads:[~2026-10-01 14:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-01 13:20 Artem Novikov
2026-10-01 13:23 ` netdev-bot+sinfo
2026-10-01 14:35   ` Новиков Артём [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=62ee20aae4004f87b03a0e618572a1c8@amicon.ru \
    --to=naa@amicon.ru \
    --cc=davem@davemloft.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lvc-project@linuxtesting.org \
    --cc=netdev-bot+sinfo@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pchelkin@ispras.ru \
    --cc=rrv@amicon.ru \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    /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®