From: Dmitry Vyukov <dvyukov@google.com>
To: David Howells <dhowells@redhat.com>
Cc: syzbot <syzbot+1e0edc4b8b7494c28450@syzkaller.appspotmail.com>,
Eric Biggers <ebiggers@kernel.org>,
David Miller <davem@davemloft.net>,
linux-afs@lists.infradead.org,
LKML <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Subject: Re: kernel BUG at net/rxrpc/local_object.c:LINE!
Date: Wed, 31 Jul 2019 17:31:45 +0200 [thread overview]
Message-ID: <CACT4Y+bjLBwVK_6fz2H8fXm0baAVX+vRJ4UbVWG_7yNUO-SOUg@mail.gmail.com> (raw)
In-Reply-To: <22318.1564586386@warthog.procyon.org.uk>
On Wed, Jul 31, 2019 at 5:19 PM David Howells <dhowells@redhat.com> wrote:
>
> Dmitry Vyukov <dvyukov@google.com> wrote:
>
> > Please send a patch for testing that enables this tracing
> > unconditionally. This should have the same effect. There is no way to
> > hook into a middle of the automated process and arbitrary tune things.
>
> I don't know how to do that off hand. Do you have an example?
Few messages above I asked it to test:
https://groups.google.com/d/msg/syzkaller-bugs/gEnZkmEWf1s/r2_X_KVQAQAJ
Basically, git repo + branch + patch. Here are the docs:
https://github.com/google/syzkaller/blob/master/docs/syzbot.md#testing-patches
> Anyway, I think rxrpc_local_processor() is broken with respect to refcounting
> as it gets scheduled when usage==0, but that doesn't stop it being rescheduled
> again by a network packet before it manages to close the UDP socket.
>
> David
next prev parent reply other threads:[~2019-07-31 15:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-28 2:47 kernel BUG at net/rxrpc/local_object.c:LINE! syzbot
2019-07-02 13:37 ` David Howells
2019-07-05 12:12 ` Dmitry Vyukov
2019-07-05 12:15 ` Dmitry Vyukov
2019-07-06 10:03 ` syzbot
2019-07-31 14:30 ` David Howells
2019-07-31 14:46 ` Dmitry Vyukov
2019-07-31 15:19 ` David Howells
2019-07-31 15:31 ` Dmitry Vyukov [this message]
2019-08-13 14:23 ` David Howells
2019-08-13 14:28 ` Dmitry Vyukov
2019-08-13 15:06 ` David Howells
2019-08-13 15:12 ` Dmitry Vyukov
2019-08-13 15:29 ` David Howells
2019-08-18 18:47 ` syzbot
[not found] <20190819071101.5796-1-hdanton@sina.com>
2019-08-19 8:23 ` David Howells
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+bjLBwVK_6fz2H8fXm0baAVX+vRJ4UbVWG_7yNUO-SOUg@mail.gmail.com \
--to=dvyukov@google.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=ebiggers@kernel.org \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzbot+1e0edc4b8b7494c28450@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.