All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Vyukov <dvyukov@google.com>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>
Cc: syzbot <syzbot+0827f43974813b74e6db@syzkaller.appspotmail.com>,
	bristot@redhat.com, bsegall@google.com, dietmar.eggemann@arm.com,
	hannes@cmpxchg.org, juri.lelli@redhat.com,
	linux-kernel@vger.kernel.org, mgorman@suse.de, mingo@redhat.com,
	peterz@infradead.org, rostedt@goodmis.org, surenb@google.com,
	syzkaller-bugs@googlegroups.com, vincent.guittot@linaro.org,
	vschneid@redhat.com,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [syzbot] upstream boot error: BUG: unable to handle kernel NULL pointer dereference in psi_task_switch
Date: Wed, 3 May 2023 12:38:19 +0200	[thread overview]
Message-ID: <CACT4Y+Zxd87dozaOgKWQ=ROpnN8-4k+ErFByJEu_oxnJttmxMg@mail.gmail.com> (raw)
In-Reply-To: <ZFI4ue1uzd0Il9yM@shell.armlinux.org.uk>

On Wed, 3 May 2023 at 12:34, Russell King (Oracle)
<linux@armlinux.org.uk> wrote:
>
> On Tue, May 02, 2023 at 08:37:15AM +0200, Dmitry Vyukov wrote:
> > On Mon, 1 May 2023 at 18:43, syzbot
> > <syzbot+0827f43974813b74e6db@syzkaller.appspotmail.com> wrote:
> > >
> > > Hello,
> > >
> > > syzbot found the following issue on:
> > >
> > > HEAD commit:    89d77f71f493 Merge tag 'riscv-for-linus-6.4-mw1' of git://..
> > > git tree:       upstream
> > > console output: https://syzkaller.appspot.com/x/log.txt?x=1113550c280000
> > > kernel config:  https://syzkaller.appspot.com/x/.config?x=4cc65ccad523b604
> > > dashboard link: https://syzkaller.appspot.com/bug?extid=0827f43974813b74e6db
> > > compiler:       arm-linux-gnueabi-gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
> > > userspace arch: arm
> > >
> > > IMPORTANT: if you fix the issue, please add the following tag to the commit:
> > > Reported-by: syzbot+0827f43974813b74e6db@syzkaller.appspotmail.com
> >
> > +arm mailing list
> >
> > Kernel started falling apart on arm during boot in various strange ways.
>
> Are these all the same hardware platform? If so, please check the
> hardware with a known working kernel. These look like spurious failts
> caused possibly the hardware platform failing.

It happens in the same qemu that used to work before. So "hardware" is
presumably working.

WARNING: multiple messages have this Message-ID (diff)
From: Dmitry Vyukov <dvyukov@google.com>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>
Cc: syzbot <syzbot+0827f43974813b74e6db@syzkaller.appspotmail.com>,
	 bristot@redhat.com, bsegall@google.com,
	dietmar.eggemann@arm.com,  hannes@cmpxchg.org,
	juri.lelli@redhat.com, linux-kernel@vger.kernel.org,
	 mgorman@suse.de, mingo@redhat.com, peterz@infradead.org,
	rostedt@goodmis.org,  surenb@google.com,
	syzkaller-bugs@googlegroups.com,  vincent.guittot@linaro.org,
	vschneid@redhat.com,
	 Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [syzbot] upstream boot error: BUG: unable to handle kernel NULL pointer dereference in psi_task_switch
Date: Wed, 3 May 2023 12:38:19 +0200	[thread overview]
Message-ID: <CACT4Y+Zxd87dozaOgKWQ=ROpnN8-4k+ErFByJEu_oxnJttmxMg@mail.gmail.com> (raw)
In-Reply-To: <ZFI4ue1uzd0Il9yM@shell.armlinux.org.uk>

On Wed, 3 May 2023 at 12:34, Russell King (Oracle)
<linux@armlinux.org.uk> wrote:
>
> On Tue, May 02, 2023 at 08:37:15AM +0200, Dmitry Vyukov wrote:
> > On Mon, 1 May 2023 at 18:43, syzbot
> > <syzbot+0827f43974813b74e6db@syzkaller.appspotmail.com> wrote:
> > >
> > > Hello,
> > >
> > > syzbot found the following issue on:
> > >
> > > HEAD commit:    89d77f71f493 Merge tag 'riscv-for-linus-6.4-mw1' of git://..
> > > git tree:       upstream
> > > console output: https://syzkaller.appspot.com/x/log.txt?x=1113550c280000
> > > kernel config:  https://syzkaller.appspot.com/x/.config?x=4cc65ccad523b604
> > > dashboard link: https://syzkaller.appspot.com/bug?extid=0827f43974813b74e6db
> > > compiler:       arm-linux-gnueabi-gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
> > > userspace arch: arm
> > >
> > > IMPORTANT: if you fix the issue, please add the following tag to the commit:
> > > Reported-by: syzbot+0827f43974813b74e6db@syzkaller.appspotmail.com
> >
> > +arm mailing list
> >
> > Kernel started falling apart on arm during boot in various strange ways.
>
> Are these all the same hardware platform? If so, please check the
> hardware with a known working kernel. These look like spurious failts
> caused possibly the hardware platform failing.

It happens in the same qemu that used to work before. So "hardware" is
presumably working.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2023-05-03 10:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-01 16:43 [syzbot] upstream boot error: BUG: unable to handle kernel NULL pointer dereference in psi_task_switch syzbot
2023-05-02  6:37 ` Dmitry Vyukov
2023-05-02  6:37   ` Dmitry Vyukov
2023-05-03 10:34   ` Russell King (Oracle)
2023-05-03 10:34     ` Russell King (Oracle)
2023-05-03 10:38     ` Dmitry Vyukov [this message]
2023-05-03 10:38       ` Dmitry Vyukov
2023-05-03 10:54       ` Russell King (Oracle)
2023-05-03 10:54         ` Russell King (Oracle)
2023-05-03 13:32 ` Peter Zijlstra
2023-05-03 16:29   ` Johannes Weiner
2023-05-04  9:56     ` Chengming Zhou
2023-05-08  6:23       ` Dmitry Vyukov

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+Zxd87dozaOgKWQ=ROpnN8-4k+ErFByJEu_oxnJttmxMg@mail.gmail.com' \
    --to=dvyukov@google.com \
    --cc=bristot@redhat.com \
    --cc=bsegall@google.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=hannes@cmpxchg.org \
    --cc=juri.lelli@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=surenb@google.com \
    --cc=syzbot+0827f43974813b74e6db@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=vincent.guittot@linaro.org \
    --cc=vschneid@redhat.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.