mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: Paolo Abeni <pabeni@redhat.com>, kuniyu@google.com
Cc: syzbot <syzbot+ff020673c5e3d94d9478@syzkaller.appspotmail.com>,
	linux-kernel@vger.kernel.org, mptcp@lists.linux.dev,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mptcp?] KMSAN: uninit-value in mptcp_established_options
Date: Fri, 29 May 2026 12:41:39 +1000	[thread overview]
Message-ID: <ba9aa82d-efd6-48c8-8e90-8820a21c5402@kernel.org> (raw)
In-Reply-To: <672f5b7d-6fa0-41c5-a950-2890028c8572@redhat.com>

Hi Paolo,

On 08/05/2026 19:27, Paolo Abeni wrote:
> On 5/7/26 9:44 AM, Matthieu Baerts wrote:
>> Hi Paolo, Kuniyuki,
>>
>> On 04/05/2026 20:20, syzbot wrote:
>>> Hello,
>>>
>>> syzbot has tested the proposed patch but the reproducer is still triggering an issue:
>>> KMSAN: uninit-value in irqentry_exit_to_kernel_mode_preempt
>>
>> It looks like the issue is different now:

(...)

>> Plus I'm not exactly sure to understand the issue here: mp_opt is
>> defined and used only in mptcp_incoming_options(), and I don't see
>> anything using it after the end of this function. Or did I miss something?
> 
> I also had hard time understanding the backtrace, I think some frames
> are omitted/missing (it happens sometime, IDK why), specifically the one
> related to mptcp_options_received() - which would be useful to
> understand the issue.

Because the other issue spot by syzbot seems to unrelated, do you plan
to send your patch upstream? Or do you prefer if someone else does it?

Cheers,
Matt
-- 
Sponsored by the NGI0 Core fund.


  parent reply	other threads:[~2026-05-29  2:41 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-01  6:15 syzbot
2026-05-03 13:01 ` syzbot
2026-05-03 14:53 ` Forwarded: [PATCH] mptcp: zero opts->ext_copy on DATA_FIN-only path syzbot
2026-05-03 23:20 ` Forwarded: [PATCH] mptcp: zero opts->ext_copy in mptcp_established_options_dss() syzbot
2026-05-04  9:51 ` [PATCH] mptcp: fix KMSAN: uninit-value in mptcp_established_options Matthieu Baerts (NGI0)
2026-05-04  9:59   ` Matthieu Baerts
2026-05-04 11:14     ` [syzbot] [mptcp?] " syzbot
2026-05-04 16:22     ` [PATCH] mptcp: fix " Paolo Abeni
2026-05-04 17:14       ` [syzbot] [mptcp?] " syzbot
2026-05-04 17:31       ` [PATCH] mptcp: fix " Paolo Abeni
2026-05-04 18:20         ` [syzbot] [mptcp?] " syzbot
2026-05-07  7:44           ` Matthieu Baerts
2026-05-08  9:27             ` Paolo Abeni
2026-05-08 10:11               ` Alexander Potapenko
2026-05-08 10:46                 ` Matthieu Baerts
2026-05-12  8:55                   ` Matthieu Baerts
2026-05-12  9:31                     ` Alexander Potapenko
2026-05-12 13:22                       ` Matthieu Baerts
2026-05-12 10:08                     ` syzbot
2026-05-29  2:41               ` Matthieu Baerts [this message]
2026-05-29  7:48                 ` Paolo Abeni
     [not found] <20260503145319.7726-1-kartikey406@gmail.com>
2026-05-03 15:47 ` syzbot
     [not found] <20260503232040.9451-1-kartikey406@gmail.com>
2026-05-04  0:08 ` syzbot

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=ba9aa82d-efd6-48c8-8e90-8820a21c5402@kernel.org \
    --to=matttbe@kernel.org \
    --cc=kuniyu@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mptcp@lists.linux.dev \
    --cc=pabeni@redhat.com \
    --cc=syzbot+ff020673c5e3d94d9478@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.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

Powered by JetHome