All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Vyukov <dvyukov@google.com>
To: Steffen Klassert <steffen.klassert@secunet.com>
Cc: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	"David S. Miller" <davem@davemloft.net>,
	syzbot <syzbot+2dfb68e639f0621b19fb@syzkaller.appspotmail.com>,
	Dan Streetman <ddstreet@ieee.org>,
	LKML <linux-kernel@vger.kernel.org>,
	netdev <netdev@vger.kernel.org>,
	syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Subject: Re: unregister_netdevice: waiting for DEV to become free
Date: Wed, 1 Aug 2018 11:14:43 +0200	[thread overview]
Message-ID: <CACT4Y+bNWOsq4ZABF67ye6SMddfffEvmdUzu9EfEr77j7XpzRA@mail.gmail.com> (raw)
In-Reply-To: <20180801085749.3nf5hbxjxoafangb@gauss3.secunet.de>

On Wed, Aug 1, 2018 at 10:57 AM, Steffen Klassert
<steffen.klassert@secunet.com> wrote:
> On Tue, Jul 31, 2018 at 01:31:52PM +0200, Steffen Klassert wrote:
>> On Tue, Jul 31, 2018 at 08:16:22PM +0900, Tetsuo Handa wrote:
>> > Steffen and Herbert,
>> >
>> > Do you have any question? I think I provided enough information for debugging.
>>
>> It seems that I was not on Cc at the beginning of the threat,
>> so I had to search the web for some context.
>>
>> I'm currently trying your reproducer (still with my .config) but I don't
>> hit the problem.
>
> Actually, I did not hit it because it is already fixed in my tree.
>
> It is fixed by:
>
> commit 8cc88773855f988d6a3bbf102bbd9dd9c828eb81
> xfrm: fix missing dst_release() after policy blocking lbcast and multicast
>
> This fix went to mainline on Monday.

Thanks, let's tell syzbot:

#syz fix:
xfrm: fix missing dst_release() after policy blocking lbcast and multicast

      reply	other threads:[~2018-08-01  9:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-19 14:52 unregister_netdevice: waiting for DEV to become free syzbot
2018-04-19 14:53 ` Dmitry Vyukov
2018-04-20 23:59 ` syzbot
2018-07-27 13:00   ` Tetsuo Handa
2018-07-31 11:16     ` Tetsuo Handa
2018-07-31 11:31       ` Steffen Klassert
2018-08-01  8:57         ` Steffen Klassert
2018-08-01  9:14           ` Dmitry Vyukov [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=CACT4Y+bNWOsq4ZABF67ye6SMddfffEvmdUzu9EfEr77j7XpzRA@mail.gmail.com \
    --to=dvyukov@google.com \
    --cc=davem@davemloft.net \
    --cc=ddstreet@ieee.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=penguin-kernel@i-love.sakura.ne.jp \
    --cc=steffen.klassert@secunet.com \
    --cc=syzbot+2dfb68e639f0621b19fb@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.