From: Mark Brown <broonie@kernel.org>
To: syzbot <syzbot+9f06ddd18bf059dff2ad@syzkaller.appspotmail.com>
Cc: akpm@linux-foundation.org, ckeepax@opensource.cirrus.com,
jfs-discussion@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, shaggy@kernel.org,
syzkaller-bugs@googlegroups.com, willy@infradead.org
Subject: Re: [syzbot] [jfs?] KASAN: invalid-free in sys_mount
Date: Tue, 21 Mar 2023 17:09:44 +0000 [thread overview]
Message-ID: <2d0114ce-a811-47e9-9a76-8c7a80f1faed@sirena.org.uk> (raw)
In-Reply-To: <000000000000698e5d05f76c0adf@google.com>
[-- Attachment #1: Type: text/plain, Size: 1078 bytes --]
On Tue, Mar 21, 2023 at 10:04:46AM -0700, syzbot wrote:
> The issue was bisected to:
>
> commit a0b6e4048228829485a43247c12c7774531728c4
> Author: Charles Keepax <ckeepax@opensource.cirrus.com>
> Date: Thu Jun 23 12:52:28 2022 +0000
>
> ASoC: cx20442: Remove now redundant non_legacy_dai_naming flag
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12756e1cc80000
> final oops: https://syzkaller.appspot.com/x/report.txt?x=11756e1cc80000
> console output: https://syzkaller.appspot.com/x/log.txt?x=16756e1cc80000
This does not seem especially credible for the backtrace provided:
> slab_free mm/slub.c:3787 [inline]
> __kmem_cache_free+0xaf/0x2d0 mm/slub.c:3800
> __do_sys_mount fs/namespace.c:3596 [inline]
> __se_sys_mount fs/namespace.c:3571 [inline]
> __x64_sys_mount+0x212/0x300 fs/namespace.c:3571
> do_syscall_x64 arch/x86/entry/common.c:50 [inline]
> do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
> entry_SYSCALL_64_after_hwframe+0x63/0xcd
which is nowhere near ASoC, let alone that specific driver.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2023-03-21 17:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 17:04 [syzbot] [jfs?] KASAN: invalid-free in sys_mount syzbot
2023-03-21 17:09 ` Mark Brown [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=2d0114ce-a811-47e9-9a76-8c7a80f1faed@sirena.org.uk \
--to=broonie@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shaggy@kernel.org \
--cc=syzbot+9f06ddd18bf059dff2ad@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=willy@infradead.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).