public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+3a92d359bc2ec6255a33@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Forwarded: Re: [syzbot] [net?] divide error in __tcp_select_window (4)
Date: Wed, 26 Nov 2025 03:53:42 -0800	[thread overview]
Message-ID: <6926ea46.a70a0220.d98e3.00d3.GAE@google.com> (raw)
In-Reply-To: <69260882.a70a0220.d98e3.00b4.GAE@google.com>

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.

***

Subject: Re: [syzbot] [net?] divide error in __tcp_select_window (4)
Author: matttbe@kernel.org

On 26/11/2025 12:51, syzbot wrote:
>> Hello,
>>
>> (+cc Paolo)
>>
>> On 26/11/2025 12:28, Matthieu Baerts wrote:
>>> Hello,
>>>
>>> (Without other ML's to test a different fix)
>>>
>>> On 25/11/2025 20:50, syzbot wrote:
>>>> Hello,
>>>>
>>>> syzbot found the following issue on:
>>>>
>>>> HEAD commit:    e2c20036a887 Merge branch 'devlink-net-mlx5-implement-swp_..
>>>> git tree:       net-next
>>>> console output: https://syzkaller.appspot.com/x/log.txt?x=1164c484580000
>>>> kernel config:  https://syzkaller.appspot.com/x/.config?x=a881ccda32df4e75
>>>> dashboard link: https://syzkaller.appspot.com/bug?extid=3a92d359bc2ec6255a33
>>>> compiler:       Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
>>>> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=13f8fa12580000
>>>> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=113a5a12580000
>>>>
>>>> Downloadable assets:
>>>> disk image: https://storage.googleapis.com/syzbot-assets/07279e689a07/disk-e2c20036.raw.xz
>>>> vmlinux: https://storage.googleapis.com/syzbot-assets/b13e2e59c1ed/vmlinux-e2c20036.xz
>>>> kernel image: https://storage.googleapis.com/syzbot-assets/f6f519394597/bzImage-e2c20036.xz
>>>>
>>>> The issue was bisected to:
>>>>
>>>> commit ae155060247be8dcae3802a95bd1bdf93ab3215d
>>>> Author: Paolo Abeni <pabeni@redhat.com>
>>>> Date:   Tue Nov 18 07:20:24 2025 +0000
>>>>
>>>>     mptcp: fix duplicate reset on fastclose
>>>>
>>>> bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=11f698b4580000
>>>> final oops:     https://syzkaller.appspot.com/x/report.txt?x=13f698b4580000
>>>> console output: https://syzkaller.appspot.com/x/log.txt?x=15f698b4580000
>>>>
>>>> IMPORTANT: if you fix the issue, please add the following tag to the commit:
>>>> Reported-by: syzbot+3a92d359bc2ec6255a33@syzkaller.appspotmail.com
>>>> Fixes: ae155060247b ("mptcp: fix duplicate reset on fastclose")
>>>
>>> I *think* this issue might have been fixed by another patch that has
>>> been sent recently, see "mptcp: clear scheduled subflows on retransmit":
>>>
>>>
>>> #syz test: git://git.kernel.org/pub/scm/linux/kernel/git/matttbe/net-next.git b4/net-mptcp-clear-sched-rtx
>>
>>
>> Mmh, sorry for the noise, I just noticed the reproducers were apparently
>> only working on top of net-next, and my branch was on top of 'net'.
>> Sending the patch with net-next as base then.
>>
>> #syz test: git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git
> 
> "Cheers," does not look like a valid git branch or commit.

Picky :)

Sorry, new attempt including the branch name (and the patch):


#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git main


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

      parent reply	other threads:[~2025-11-26 11:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-25 19:50 [syzbot] [net?] divide error in __tcp_select_window (4) syzbot
2025-11-26 11:29 ` Forwarded: " syzbot
2025-11-26 11:53 ` syzbot [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=6926ea46.a70a0220.d98e3.00d3.GAE@google.com \
    --to=syzbot+3a92d359bc2ec6255a33@syzkaller.appspotmail.com \
    --cc=linux-kernel@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