public inbox for mptcp@lists.linux.dev
 help / color / mirror / Atom feed
From: Matthieu Baerts <matttbe@kernel.org>
To: syzbot <syzbot+9475dcc0b42355ded022@syzkaller.appspotmail.com>
Cc: geliang@kernel.org, linux-kernel@vger.kernel.org,
	martineau@kernel.org, mptcp@lists.linux.dev, pabeni@redhat.com,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mptcp?] WARNING in __mptcp_move_skbs_from_subflow (2)
Date: Fri, 13 Feb 2026 12:01:15 +0100	[thread overview]
Message-ID: <12774ad8-6d81-4dc1-b3af-e62f623b467a@kernel.org> (raw)
In-Reply-To: <692056f6.a70a0220.2ea503.004e.GAE@google.com>

Hello,

-cc netdev & maintainers

On 21/11/2025 13:11, syzbot wrote:
> Hello,
> 
> syzbot found the following issue on:
> 
> HEAD commit:    fd95357fd8c6 Merge tag 'sched_ext-for-6.18-rc6-fixes-2' of..
> git tree:       upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=17220e92580000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=1cd7f786c0f5182f
> dashboard link: https://syzkaller.appspot.com/bug?extid=9475dcc0b42355ded022
> compiler:       gcc (Debian 12.2.0-14+deb12u1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
> userspace arch: i386
> 
> Unfortunately, I don't have any reproducer for this issue yet.
> 
> Downloadable assets:
> disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-fd95357f.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/9301ea2e80a9/vmlinux-fd95357f.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/13592a9d2a74/bzImage-fd95357f.xz
> 
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+9475dcc0b42355ded022@syzkaller.appspotmail.com

This bug has not been seen for quite a while, and we didn't find
anything wrong when looking at the related code. We then think it was
induced by a previous memory corruption. It can be re-opened if needed.

#syz invalid

Ref on our side:

  https://github.com/multipath-tcp/mptcp_net-next/issues/608

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


      reply	other threads:[~2026-02-13 11:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-21 12:11 [syzbot] [mptcp?] WARNING in __mptcp_move_skbs_from_subflow (2) syzbot
2026-02-13 11:01 ` Matthieu Baerts [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=12774ad8-6d81-4dc1-b3af-e62f623b467a@kernel.org \
    --to=matttbe@kernel.org \
    --cc=geliang@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martineau@kernel.org \
    --cc=mptcp@lists.linux.dev \
    --cc=pabeni@redhat.com \
    --cc=syzbot+9475dcc0b42355ded022@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