Hi Hillf,
There are some commits in net/master that ought to fix this and conflict with
your longer patch:
730c5fd42c1e3652a065448fd235cb9fafb2bd10
rxrpc: Fix local endpoint refcounting
68553f1a6f746bf860bce3eb42d78c26a717d9c0
rxrpc: Fix local refcounting
syzbot has found a reproducer for the following crash on:
HEAD commit:0c3d3d64 Add linux-next specific files for 20190816
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=108b58f260
kernel config: https://syzkaller.appspot.com/x/.config?x=dffdf1e146f94
Dmitry Vyukov wrote:
> It only collects console output. I don't know what is trace log. If
> the trace log is not console output, then it won't.
Assuming the system is still alive:
cat /sys/kernel/debug/tracing/trace
David
On Tue, Aug 13, 2019 at 5:06 PM David Howells wrote:
>
> Dmitry Vyukov wrote:
>
> > > I meant that I don't know how to turn a tracepoint on from inside the
> > > kernel.
> >
> > This /sys/kernel/debug/tracing/events/rxrpc/rxrpc_local/enable in:
> > echo 1 > /sys/kernel/debug/tracing/even
Dmitry Vyukov wrote:
> > I meant that I don't know how to turn a tracepoint on from inside the
> > kernel.
>
> This /sys/kernel/debug/tracing/events/rxrpc/rxrpc_local/enable in:
> echo 1 > /sys/kernel/debug/tracing/events/rxrpc/rxrpc_local/enable
> should map to some global variable, ri
On Tue, Aug 13, 2019 at 4:23 PM David Howells wrote:
>
> Dmitry Vyukov 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 th
Dmitry Vyukov 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
On Wed, Jul 31, 2019 at 5:19 PM David Howells wrote:
>
> Dmitry Vyukov 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
Dmitry Vyukov 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?
Anyway
On Wed, Jul 31, 2019 at 4:30 PM David Howells wrote:
>
> Dmitry Vyukov wrote:
>
> > Re bisection, I don't know if there are some more subtle things as
> > play (you are in the better position to judge that), but bisection log
> > looks good, it tracked the target crash throughout and wasn't
> > d
Dmitry Vyukov wrote:
> Re bisection, I don't know if there are some more subtle things as
> play (you are in the better position to judge that), but bisection log
> looks good, it tracked the target crash throughout and wasn't
> distracted by any unrelated bugs, etc. So I don't see any obvious
>
Hello,
syzbot has tested the proposed patch but the reproducer still triggered
crash:
kernel BUG at net/rxrpc/local_object.c:LINE!
rxrpc: Assertion failed
[ cut here ]
kernel BUG at net/rxrpc/local_object.c:468!
invalid opcode: [#1] PREEMPT SMP KASAN
CPU: 1 PID
On Fri, Jul 5, 2019 at 2:12 PM Dmitry Vyukov wrote:
> > syzbot wrote:
> >
> > I *think* the reproducer boils down to the attached, but I can't get
> > syzkaller
> > to work and the attached sample does not cause the oops to occur. Can you
> > try
> > it in your environment?
> >
> > > The bug w
,On Tue, Jul 2, 2019 at 3:37 PM David Howells wrote:
>
> syzbot wrote:
>
> I *think* the reproducer boils down to the attached, but I can't get syzkaller
> to work and the attached sample does not cause the oops to occur. Can you try
> it in your environment?
>
> > The bug was bisected to:
> >
>
syzbot wrote:
I *think* the reproducer boils down to the attached, but I can't get syzkaller
to work and the attached sample does not cause the oops to occur. Can you try
it in your environment?
> The bug was bisected to:
>
> commit 46894a13599a977ac35411b536fb3e0b2feefa95
> Author: David Howe
Hello,
syzbot found the following crash on:
HEAD commit:249155c2 Merge branch 'parisc-5.2-4' of git://git.kernel.o..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14fabe45a0
kernel config: https://syzkaller.appspot.com/x/.config?x=e7c31a94f66cc0aa
da
16 matches
Mail list logo
