From: Greg KH <gregkh@linuxfoundation.org>
To: Alexandre Bard <alexandre.bard@belden.com>
Cc: stable@vger.kernel.org, sashal@kernel.org,
justin.iurman@gmail.com, kuba@kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 6.12] net: ioam6: fix OOB and missing lock
Date: Mon, 31 Aug 2026 13:57:31 +0200 [thread overview]
Message-ID: <2026083122-chalice-shading-bb56@gregkh> (raw)
In-Reply-To: <20260825140732.220188-1-alexandre.bard@belden.com>
On Tue, Aug 25, 2026 at 02:07:32PM +0000, Alexandre Bard wrote:
> **********************************************************************
> DISCLAIMER:
> Privileged and/or Confidential information may be contained in this message. If you are not the addressee of this message, you may not copy, use or deliver this message to anyone. In such event, you should destroy the message and kindly notify the sender by reply e-mail. It is understood that opinions or conclusions that do not relate to the official business of the company are neither given nor endorsed by the company. Thank You.
Now deleted.
parent reply other threads:[~2026-08-31 11:57 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20260825140732.220188-1-alexandre.bard@belden.com>]
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=2026083122-chalice-shading-bb56@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=alexandre.bard@belden.com \
--cc=justin.iurman@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--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