From: Florian Westphal <fw at strlen.de>
To: mptcp at lists.01.org
Subject: [MPTCP] Re: WARNING in dst_release
Date: Thu, 18 Feb 2021 15:06:28 +0100 [thread overview]
Message-ID: <20210218140628.GD22944@breakpoint.cc> (raw)
In-Reply-To: 00000000000002cc3e05bb9c8436@google.com
[-- Attachment #1: Type: text/plain, Size: 355 bytes --]
syzbot <syzbot+b53bbea2ad64f9cf80d8(a)syzkaller.appspotmail.com> wrote:
> Hello,
>
> syzbot has tested the proposed patch and the reproducer did not trigger any issue:
>
> Reported-and-tested-by: syzbot+b53bbea2ad64f9cf80d8(a)syzkaller.appspotmail.com
#syz-fix: mptcp: reset last_snd on subflow close
[ This patch is currently in mptcp-next ]
reply other threads:[~2021-02-18 14:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210218140628.GD22944@breakpoint.cc \
--to=mptcp@lists.linux.dev \
/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