From: Thomas Gleixner <tglx@linutronix.de>
To: syzbot <syzbot+51c9bdfa559769d2f897@syzkaller.appspotmail.com>,
akpm@linux-foundation.org, anna.schumaker@netapp.com,
bfields@fieldses.org, bp@alien8.de, davem@davemloft.net,
douly.fnst@cn.fujitsu.com, hpa@zytor.com, jlayton@kernel.org,
konrad.wilk@oracle.com, len.brown@intel.com,
linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org,
mingo@kernel.org, mingo@redhat.com, netdev@vger.kernel.org,
paulmck@kernel.org, peterz@infradead.org, puwen@hygon.cn,
rafael.j.wysocki@intel.com, syzkaller-bugs@googlegroups.com,
trond.myklebust@hammerspace.com, trond.myklebust@primarydata.com,
vbabka@suse.cz, x86@kernel.org,
David Howells <dhowells@redhat.com>
Subject: Re: WARNING: ODEBUG bug in __do_softirq
Date: Wed, 26 Aug 2020 13:03:02 +0200 [thread overview]
Message-ID: <87v9h5vfdl.fsf@nanos.tec.linutronix.de> (raw)
In-Reply-To: <000000000000e7fab005adc3f636@google.com>
On Wed, Aug 26 2020 at 01:54, syzbot wrote:
Cc+: David Howells
> syzbot has found a reproducer for the following issue on:
>
> HEAD commit: 3a00d3df Add linux-next specific files for 20200825
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=15080fa9900000
> kernel config: https://syzkaller.appspot.com/x/.config?x=9ef0a5f95935d447
> dashboard link: https://syzkaller.appspot.com/bug?extid=51c9bdfa559769d2f897
> compiler: gcc (GCC) 10.1.0-syz 20200507
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17927a2e900000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=132b8ede900000
>
> The issue was bisected to:
>
> commit 5b317cbf2bcb85a1e96ce87717cb991ecab1dd4d
> Author: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> Date: Fri Feb 22 09:17:11 2019 +0000
>
> Merge branch 'pm-cpufreq-fixes'
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=171ead5d200000
> final oops: https://syzkaller.appspot.com/x/report.txt?x=149ead5d200000
> console output: https://syzkaller.appspot.com/x/log.txt?x=109ead5d200000
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+51c9bdfa559769d2f897@syzkaller.appspotmail.com
> Fixes: 5b317cbf2bcb ("Merge branch 'pm-cpufreq-fixes'")
>
> ------------[ cut here ]------------
> ODEBUG: free active (active state 0) object type: work_struct hint: afs_manage_cell+0x0/0x11c0 fs/afs/cell.c:498
AFS is leaking an active work struct in a to be freed data struct.
Thanks,
tglx
prev parent reply other threads:[~2020-08-26 11:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <001a1143e62eb6a9510565640e76@google.com>
2018-06-29 8:58 ` WARNING: ODEBUG bug in __do_softirq syzbot
2019-04-02 5:04 ` syzbot
2019-04-02 8:26 ` Borislav Petkov
2020-08-26 8:54 ` syzbot
2020-08-26 11:03 ` Thomas Gleixner [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=87v9h5vfdl.fsf@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=anna.schumaker@netapp.com \
--cc=bfields@fieldses.org \
--cc=bp@alien8.de \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=douly.fnst@cn.fujitsu.com \
--cc=hpa@zytor.com \
--cc=jlayton@kernel.org \
--cc=konrad.wilk@oracle.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=puwen@hygon.cn \
--cc=rafael.j.wysocki@intel.com \
--cc=syzbot+51c9bdfa559769d2f897@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=trond.myklebust@hammerspace.com \
--cc=trond.myklebust@primarydata.com \
--cc=vbabka@suse.cz \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).