All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: Alexander Potapenko <glider@google.com>
Cc: Paolo Abeni <pabeni@redhat.com>,
	kuniyu@google.com,
	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: Tue, 12 May 2026 15:22:26 +0200	[thread overview]
Message-ID: <a009da4e-35bf-4db1-b722-693a796f602d@kernel.org> (raw)
In-Reply-To: <CAG_fn=Wq87q5wGZt6_c_jutS1yKC+Yv1CsOOfcO03pZBVWzTdg@mail.gmail.com>

Hi Alexander,

On 12/05/2026 11:31, Alexander Potapenko wrote:
>>>>>> 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.
>>>>
>>>> This is probably related to
>>>> https://lore.kernel.org/all/69e7ee1f.a00a0220.17a17.001d.GAE@google.com/T/
>>>
>>> Ah yes, it looks similar.
>>>
>>>> Let me send the patch, perhaps this issue will also go away.
>>>
>>> That would be great, thank you!
>>
>> Thank you for having sent your patch.
>>
>> Here is one combining your modifications, and the ones from Paolo, for
>> syzbot. If this one is OK, we can continue with Paolo's patch.
> 
> 
> Hi Matt,
> 
> Unfortunately my approach was wrong: see tglx's response there.
> Hope we'll figure something out (__no_kmsan_checks looks promising)
Thank you for your reply, I just found the email thread you mentioned:

  https://lore.kernel.org/all/87v7cu876c.ffs@tglx

If a v2 is not expected "soon", I'm sure we can continue with Paolo's
patch, and double-check later to see if it was enough.

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


  reply	other threads:[~2026-05-12 13:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-01  6:15 [syzbot] [mptcp?] KMSAN: uninit-value in mptcp_established_options syzbot
2026-05-03 13:01 ` syzbot
2026-05-04  9:51 ` [PATCH] mptcp: fix " 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 [this message]
2026-05-12 10:08                     ` syzbot
2026-05-04 11:02   ` [PATCH] mptcp: fix " MPTCP CI

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=a009da4e-35bf-4db1-b722-693a796f602d@kernel.org \
    --to=matttbe@kernel.org \
    --cc=glider@google.com \
    --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 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.