linux-kernel - Re: [syzbot] [trace?] WARNING in tracepoint_probe

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CACT4Y+YrQR5HQWZuWb9OrupPR0C=mvLyWcJN3ofuUyf7j-nGRA@mail.gmail.com>
Date: Wed, 18 Dec 2024 11:09:31 +0100
From: Dmitry Vyukov <dvyukov@...gle.com>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: syzbot <syzbot+a1d25e53cd4a10f7f2d3@...kaller.appspotmail.com>, 
	linux-kernel@...r.kernel.org, linux-trace-kernel@...r.kernel.org, 
	mathieu.desnoyers@...icios.com, mhiramat@...nel.org, 
	syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] [trace?] WARNING in tracepoint_probe_unregister (3)

On Tue, 17 Dec 2024 at 22:47, Steven Rostedt <rostedt@...dmis.org> wrote:
>
> On Tue, 17 Dec 2024 13:14:29 -0800
> syzbot <syzbot+a1d25e53cd4a10f7f2d3@...kaller.appspotmail.com> wrote:
>
> > Hello,
> >
> > syzbot found the following issue on:
> >
> > HEAD commit:    243f750a2df0 Merge tag 'gpio-fixes-for-v6.13-rc3' of git:/..
> > git tree:       upstream
> > console output: https://syzkaller.appspot.com/x/log.txt?x=1310a4f8580000
> > kernel config:  https://syzkaller.appspot.com/x/.config?x=99a5586995ec03b2
> > dashboard link: https://syzkaller.appspot.com/bug?extid=a1d25e53cd4a10f7f2d3
> > compiler:       gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
> >
> > Unfortunately, I don't have any reproducer for this issue yet.
> >
> > Downloadable assets:
> > disk image: https://storage.googleapis.com/syzbot-assets/939c742e99e7/disk-243f750a.raw.xz
> > vmlinux: https://storage.googleapis.com/syzbot-assets/76db565b11d6/vmlinux-243f750a.xz
> > kernel image: https://storage.googleapis.com/syzbot-assets/822230eb0753/bzImage-243f750a.xz
> >
> > IMPORTANT: if you fix the issue, please add the following tag to the commit:
> > Reported-by: syzbot+a1d25e53cd4a10f7f2d3@...kaller.appspotmail.com
> >
>
> BTW,
>
> If you are injecting faults and hitting bugs when you do.
>
>    PLEASE REPORT YOU ARE INJECTING FAULTS!!!
>
> It just happened that I looked at the above console output to know that.
> Without that information, this would never be solved, as the memory
> failures you are injecting are for things that are less than a page and
> would only happen when the system is dangerously low on memory.
>
> Knowing that this was caused after fault injection is critical knowledge!
>
> Without that knowledge, this can be a big waste of time for maintainers who
> will go off on wild goose chases trying to figure out what's wrong with the
> logic, when it really was simply a missed check of something that didn't
> get allocated, that would also never not get allocated unless the system
> was in dire straits.

Hi Steve,

I've filed https://github.com/google/syzkaller/issues/5621 to not lose
this request. Thanks for the feedback.