Hello,
syzbot found the following issue on:
HEAD commit:d93a0d43 Merge tag 'block-5.12-2021-04-02' of git://git.ke..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16519431d0
kernel config: https://syzkaller.appspot.com/x/.config?x=71a75beb62b62a34
On 11/04/2021 09:58, Hao Sun wrote:
> Pavel Begunkov 于2021年4月11日周日 下午4:14写道：
>>
>> On 11/04/2021 04:08, Hao Sun wrote:
>>> Hi
>>>
>>> When using Healer(https://github.com/SunHao-0/healer/tree/dev) to fuzz
>>> the Linux kernel, I found a null-ptr-deref bug in
>>> io_uring_cancel_task_requests
Pavel Begunkov 于2021年4月11日周日 下午4:14写道：
>
> On 11/04/2021 04:08, Hao Sun wrote:
> > Hi
> >
> > When using Healer(https://github.com/SunHao-0/healer/tree/dev) to fuzz
> > the Linux kernel, I found a null-ptr-deref bug in
> > io_uring_cancel_task_requests under fault injection condition, but I'm
> >
On 11/04/2021 04:08, Hao Sun wrote:
> Hi
>
> When using Healer(https://github.com/SunHao-0/healer/tree/dev) to fuzz
> the Linux kernel, I found a null-ptr-deref bug in
> io_uring_cancel_task_requests under fault injection condition, but I'm
> not sure about this.
> Sorry, I do not have a
Hi
When using Healer(https://github.com/SunHao-0/healer/tree/dev) to fuzz
the Linux kernel, I found a null-ptr-deref bug in
io_uring_cancel_task_requests under fault injection condition, but I'm
not sure about this.
Sorry, I do not have a reproducing program for this bug.
I hope that the stack
Hi
When using Healer(https://github.com/SunHao-0/healer/tree/dev) to fuzz
the Linux kernel, I found a null-ptr-deref bug in do_epoll_wait, but
I'm not sure about this.
Sorry, I do not have a reproducing program for this bug.
I hope that the stack trace information in the crash log can help you
On 3/10/21 7:55 PM, Maxim Mikityanskiy wrote:
> On 2021-03-10 19:03, Eric Dumazet wrote:
>>
>>
>> On 3/10/21 3:54 PM, Maxim Mikityanskiy wrote:
>>> On 2021-03-09 17:20, Eric Dumazet wrote:
On 3/9/21 4:13 PM, syzbot wrote:
> Hello,
>
> syzbot found the following issue
On 2021-03-10 19:03, Eric Dumazet wrote:
On 3/10/21 3:54 PM, Maxim Mikityanskiy wrote:
On 2021-03-09 17:20, Eric Dumazet wrote:
On 3/9/21 4:13 PM, syzbot wrote:
Hello,
syzbot found the following issue on:
HEAD commit: 38b5133a octeontx2-pf: Fix otx2_get_fecparam()
git tree:
On 3/10/21 3:54 PM, Maxim Mikityanskiy wrote:
> On 2021-03-09 17:20, Eric Dumazet wrote:
>>
>>
>> On 3/9/21 4:13 PM, syzbot wrote:
>>> Hello,
>>>
>>> syzbot found the following issue on:
>>>
>>> HEAD commit: 38b5133a octeontx2-pf: Fix otx2_get_fecparam()
>>> git tree: net-next
>>>
On 2021-03-09 17:20, Eric Dumazet wrote:
On 3/9/21 4:13 PM, syzbot wrote:
Hello,
syzbot found the following issue on:
HEAD commit:38b5133a octeontx2-pf: Fix otx2_get_fecparam()
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=166288a8d0
kernel
On 3/9/21 4:13 PM, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit:38b5133a octeontx2-pf: Fix otx2_get_fecparam()
> git tree: net-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=166288a8d0
> kernel config:
Hello,
syzbot found the following issue on:
HEAD commit:38b5133a octeontx2-pf: Fix otx2_get_fecparam()
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=166288a8d0
kernel config: https://syzkaller.appspot.com/x/.config?x=dbc1ca9e55dc1f9f
dashboard link:
Hello,
syzbot found the following issue on:
HEAD commit:5695e516 Merge tag 'io_uring-worker.v3-2021-02-25' of git:..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10bc7b96d0
kernel config: https://syzkaller.appspot.com/x/.config?x=e33ab2de74f48295
On Wed, Feb 24, 2021 at 1:58 PM syzbot
wrote:
>
> syzbot has bisected this issue to:
>
> commit 97593cad003c668e2532cb2939a24a031f8de52d
> Author: Andrey Konovalov
> Date: Tue Dec 22 20:03:28 2020 +
>
> kasan: sanitize objects when metadata doesn't fit
>
> bisection log:
syzbot has bisected this issue to:
commit 97593cad003c668e2532cb2939a24a031f8de52d
Author: Andrey Konovalov
Date: Tue Dec 22 20:03:28 2020 +
kasan: sanitize objects when metadata doesn't fit
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=106689b6d0
start commit:
On Sun, Jan 17, 2021 at 03:29:05AM -0800, syzbot wrote:
> syzbot has bisected this issue to:
>
> commit ea40d7857d5250e5400f38c69ef9e17321e9c4a2
> Author: Daniel Vetter
> Date: Fri Oct 9 23:21:56 2020 +
>
> drm/vkms: fbdev emulation support
Not sure you want to annotate this, but
syzbot has bisected this issue to:
commit ea40d7857d5250e5400f38c69ef9e17321e9c4a2
Author: Daniel Vetter
Date: Fri Oct 9 23:21:56 2020 +
drm/vkms: fbdev emulation support
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=148e2748d0
start commit: b3a3cbde Add
syzbot has found a reproducer for the following issue on:
HEAD commit:b3a3cbde Add linux-next specific files for 20210115
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=164096d750
kernel config:
On Sat, Jan 9, 2021 at 8:20 AM syzbot
wrote:
>
> syzbot suspects this issue was fixed by commit:
>
> commit d24396c5290ba8ab04ba505176874c4e04a2d53c
> Author: Rustam Kovhaev
> Date: Sun Nov 1 14:09:58 2020 +
>
> reiserfs: add check for an invalid ih_entry_count
>
> bisection log:
syzbot suspects this issue was fixed by commit:
commit d24396c5290ba8ab04ba505176874c4e04a2d53c
Author: Rustam Kovhaev
Date: Sun Nov 1 14:09:58 2020 +
reiserfs: add check for an invalid ih_entry_count
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=111480e750
start
On Sun, 2020-12-27 at 20:51 +0100, Dmitry Vyukov wrote:
> /\/\/\/\On Sun, Dec 27, 2020 at 8:45 PM Andrew Morton
> wrote:
> >
> > (cc KASAN developers)
> >
> > On Sat, 26 Dec 2020 15:25:14 -0800 syzbot
> > wrote:
> >
> > > Hello,
> > >
> > > syzbot found the following issue on:
> > >
> > > HEAD
/\/\/\/\On Sun, Dec 27, 2020 at 8:45 PM Andrew Morton
wrote:
>
> (cc KASAN developers)
>
> On Sat, 26 Dec 2020 15:25:14 -0800 syzbot
> wrote:
>
> > Hello,
> >
> > syzbot found the following issue on:
> >
> > HEAD commit:614cb589 Merge tag 'acpi-5.11-rc1-2' of git://git.kernel.o..
> > git
(cc KASAN developers)
On Sat, 26 Dec 2020 15:25:14 -0800 syzbot
wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit:614cb589 Merge tag 'acpi-5.11-rc1-2' of git://git.kernel.o..
> git tree: upstream
> console output:
Hello,
syzbot found the following issue on:
HEAD commit:614cb589 Merge tag 'acpi-5.11-rc1-2' of git://git.kernel.o..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10a82a50d0
kernel config: https://syzkaller.appspot.com/x/.config?x=bf519e1e96191576
syzbot has found a reproducer for the following issue on:
HEAD commit:a68a0262 mm/madvise: remove racy mm ownership check
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15b3609750
kernel config:
Hello,
syzbot found the following issue on:
HEAD commit:6dd65e60 Add linux-next specific files for 20201110
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1276af6250
kernel config: https://syzkaller.appspot.com/x/.config?x=4fab43daf5c54712
dashboard
On Wed, Nov 11, 2020 at 8:27 PM Lorenzo Stoakes wrote:
>
> On Wed, 11 Nov 2020 at 17:44, Andrey Konovalov wrote:
> > I'll try to reproduce this and figure out the issue. Thanks for letting us
> > know!
>
> I hope you don't mind me diving in here, I was taking a look just now
> and managed to
On Wed, 11 Nov 2020 at 17:44, Andrey Konovalov wrote:
> I'll try to reproduce this and figure out the issue. Thanks for letting us
> know!
I hope you don't mind me diving in here, I was taking a look just now
and managed to reproduce this locally - I bisected the issue to
105397399 ("kasan:
On Wed, Nov 11, 2020 at 5:26 PM Qian Cai wrote:
>
> It looks to me the code paths below had recently been modified heavily by this
> patchset. If this is reproducible, it can be confirmed by reverting it.
>
> https://lore.kernel.org/linux-arm-kernel/cover.1605046662.git.andreyk...@google.com/
It looks to me the code paths below had recently been modified heavily by this
patchset. If this is reproducible, it can be confirmed by reverting it.
https://lore.kernel.org/linux-arm-kernel/cover.1605046662.git.andreyk...@google.com/
On Tue, 2020-11-10 at 23:45 -0800, syzbot wrote:
> Hello,
>
Hello,
syzbot found the following issue on:
HEAD commit:3e14f70c Add linux-next specific files for 2020
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=12e6af6250
kernel config: https://syzkaller.appspot.com/x/.config?x=d6f4c7e100b61b76
dashboard
Hello,
syzbot found the following issue on:
HEAD commit:7c7ec322 Merge tag 'for-linus' of git://git.kernel.org/pub..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1728977390
kernel config: https://syzkaller.appspot.com/x/.config?x=240e2ebab67245c7
On Mon, Sep 21, 2020 at 12:35 PM Dmitry Vyukov wrote:
>
> On Mon, Sep 21, 2020 at 12:34 PM syzbot
> wrote:
> >
> > Hello,
> >
> > syzbot found the following issue on:
> >
> > HEAD commit:92ab97ad Merge tag 'sh-for-5.9-part2' of git://git.libc.or..
> > git tree: upstream
> > console
On Mon, Sep 21, 2020 at 12:34 PM syzbot
wrote:
>
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit:92ab97ad Merge tag 'sh-for-5.9-part2' of git://git.libc.or..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=162d70d390
> kernel
Hello,
syzbot found the following issue on:
HEAD commit:92ab97ad Merge tag 'sh-for-5.9-part2' of git://git.libc.or..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=162d70d390
kernel config: https://syzkaller.appspot.com/x/.config?x=cd992d74d6c7e62
Hello,
syzbot found the following issue on:
HEAD commit:34d4ddd3 Merge tag 'linux-kselftest-5.9-rc5' of git://git...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=147c760d90
kernel config: https://syzkaller.appspot.com/x/.config?x=a9075b36a6ae26c9
Hello,
syzbot found the following issue on:
HEAD commit:15bc20c6 Merge tag 'tty-5.9-rc3' of git://git.kernel.org/p..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15d432fe90
kernel config: https://syzkaller.appspot.com/x/.config?x=978db74cb30aa994
On 8/10/20 9:46 AM, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit:9420f1ce Merge tag 'pinctrl-v5.9-1' of git://git.kernel.or..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=13662f6290
> kernel config:
Hello,
syzbot found the following issue on:
HEAD commit:9420f1ce Merge tag 'pinctrl-v5.9-1' of git://git.kernel.or..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13662f6290
kernel config: https://syzkaller.appspot.com/x/.config?x=72cf85e4237850c8
Eric Dumazet wrote:
>
>
> On 8/2/20 3:45 PM, syzbot wrote:
> > Hello,
> >
> > syzbot found the following issue on:
> >
> > HEAD commit:ac3a0c84 Merge git://git.kernel.org/pub/scm/linux/kernel/g..
> > git tree: upstream
> > console output:
On 8/2/20 3:45 PM, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit:ac3a0c84 Merge git://git.kernel.org/pub/scm/linux/kernel/g..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=1323497090
> kernel config:
Hello,
syzbot found the following issue on:
HEAD commit:ac3a0c84 Merge git://git.kernel.org/pub/scm/linux/kernel/g..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1323497090
kernel config: https://syzkaller.appspot.com/x/.config?x=c0cfcf935bcc94d2
Hello,
On Sun, 2020-07-26 at 01:03 -0700, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit:23ee3e4e Merge tag 'pci-v5.8-fixes-2' of
> git://git.kernel...
> git tree: upstream
> console output:
> https://syzkaller.appspot.com/x/log.txt?x=14a4c7d890
>
Hello,
syzbot found the following issue on:
HEAD commit:23ee3e4e Merge tag 'pci-v5.8-fixes-2' of git://git.kernel...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14a4c7d890
kernel config: https://syzkaller.appspot.com/x/.config?x=f87a5e4232fdb267
Hello,
syzbot found the following crash on:
HEAD commit:cb8e59cc Merge git://git.kernel.org/pub/scm/linux/kernel/g..
git tree: bpf-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1446cfd310
kernel config: https://syzkaller.appspot.com/x/.config?x=a16ddbc78955e3a9
Hello,
syzbot found the following crash on:
HEAD commit:4e99b321 Merge tag 'nfs-for-5.8-2' of git://git.linux-nfs...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=116abdd310
kernel config: https://syzkaller.appspot.com/x/.config?x=bf3aec367b9ab569
On Mon, Jun 29, 2020 at 09:31:16AM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:4e99b321 Merge tag 'nfs-for-5.8-2' of git://git.linux-nfs...
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=116abdd310
>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger crash:
Reported-and-tested-by: syzbot+bca9799bf12925619...@syzkaller.appspotmail.com
Tested on:
commit: 5749fe5a ext4: avoid race conditions when remounting with ..
git tree:
#syz test: https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git
5749fe5af3db176659978718ddaecebb450cdb6b
Hello,
syzbot has tested the proposed patch but the reproducer still triggered crash:
BUG: unable to handle kernel NULL pointer dereference in generic_perform_write
BUG: kernel NULL pointer dereference, address:
#PF: supervisor instruction fetch in kernel mode
#PF: error_code
#syz test: https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git
5b8b9d0c6d0e0f1993c6c56deaf9646942c49d94
Hello,
syzbot tried to test the proposed patch but build/boot failed:
syzkaller build failed: failed to run ["make" "target"]: exit status 2
GOOS=linux GOARCH=amd64 go install ./syz-fuzzer
# github.com/google/syzkaller/sys/netbsd/gen
sys/netbsd/gen/amd64.go:41:58: undefined: Field
#syz test: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
5b8b9d0c6d0e0f1993c6c56deaf9646942c49d94
ormation, and does seem to be a
> > > workaround.
> > >
> > > Like you, I have my home directory on a separate NILFS2 filesystem. As
> > > a temporary solution, I removed the line from /etc/fstab for that
> > > filesystem and added your dd s
tion along with a manual mount of
> the home filesystem to /etc/rc.local. /home is now mounted properly
> at boot with any of the newer kernels I tried.
>
> Thanks,
> Tom
>
> On 4/30/20 5:38 AM, Hideki EIRAKU wrote:
>>> In Msg <874kuapb2s@logand.com>;
>>
of the
home filesystem to /etc/rc.local. /home is now mounted properly at boot
with any of the newer kernels I tried.
Thanks,
Tom
On 4/30/20 5:38 AM, Hideki EIRAKU wrote:
In Msg <874kuapb2s@logand.com>;
Subject "Re: BUG: unable to handle kernel NULL pointer dereference at
0
> In Msg <874kuapb2s@logand.com>;
>Subject "Re: BUG: unable to handle kernel NULL pointer dereference at
> 00a8 in nilfs_segctor_do_construct":
>
>> Tomas Hlavaty writes:
>>>>> 2) Can you mount the corrupted(?) partition from
syzbot has bisected this bug to:
commit 77cd0d7b3f257fd0e3096b4fdcff1a7d38e99e10
Author: Magnus Karlsson
Date: Wed Aug 14 07:27:17 2019 +
xsk: add support for need_wakeup flag in AF_XDP rings
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17848acd60
start commit:
On Mon, Sep 30, 2019 at 9:17 AM syzbot
wrote:
>
> Hello,
>
> syzbot found the following crash on:
Thank you Mr Syzcaller. I am on it.
/Magnus
> HEAD commit:a3c0e7b1 Merge tag 'libnvdimm-fixes-5.4-rc1' of git://git...
> git tree: upstream
> console output:
Hello,
syzbot found the following crash on:
HEAD commit:a3c0e7b1 Merge tag 'libnvdimm-fixes-5.4-rc1' of git://git...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14f0543560
kernel config: https://syzkaller.appspot.com/x/.config?x=6ffbfa7e4a36190f
On 9/16/19 9:49 AM, Cong Wang wrote:
On Mon, Sep 16, 2019 at 6:29 AM syzbot
wrote:
Hello,
syzbot found the following crash on:
HEAD commit:f4b752a6 mlx4: fix spelling mistake "veify" -> "verify"
git tree: net
console output: https://syzkaller.appspot.com/x/log.txt?x=16cbebe660
On Mon, Sep 16, 2019 at 6:29 AM syzbot
wrote:
>
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:f4b752a6 mlx4: fix spelling mistake "veify" -> "verify"
> git tree: net
> console output: https://syzkaller.appspot.com/x/log.txt?x=16cbebe660
> kernel config:
Hello,
syzbot found the following crash on:
HEAD commit:f4b752a6 mlx4: fix spelling mistake "veify" -> "verify"
git tree: net
console output: https://syzkaller.appspot.com/x/log.txt?x=16cbebe660
kernel config: https://syzkaller.appspot.com/x/.config?x=b89bb446a3faaba4
dashboard
Hello,
syzbot found the following crash on:
HEAD commit:0e5b36bc r8152: adjust the settings of ups flags
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=10e5ad7660
kernel config: https://syzkaller.appspot.com/x/.config?x=67b69b427c3b2dbf
dashboard
Hello,
syzbot found the following crash on:
HEAD commit:57c722e9 net/tls: swap sk_write_space on close
git tree: net
console output: https://syzkaller.appspot.com/x/log.txt?x=13e6c6ee60
kernel config: https://syzkaller.appspot.com/x/.config?x=a4c9e9f08e9e8960
dashboard link:
Hello,
syzbot found the following crash on:
HEAD commit:4b972a01 Linux 5.2-rc6
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17852b6ea0
kernel config: https://syzkaller.appspot.com/x/.config?x=e7c31a94f66cc0aa
dashboard link:
If vimc module is removed while streaming is active, vimc_exit runs
into NULL pointer dereference error when streaming thread tries to
access and lock graph_mutex in the struct media_device.
media_device is embedded in struct vimc_device and when vimc is removed
vimc_device and the embedded
syzbot has bisected this bug to:
commit 162f812f23bab583f5d514ca0e4df67797ac9cdf
Author: Loic Poulain
Date: Mon Sep 19 14:29:27 2016 +
Bluetooth: hci_uart: Add Marvell support
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=112f0a3b20
start commit: 162f812f
fix the bug, please add the following tag to the commit:
Reported-by: syzbot+79337b501d6aa974d...@syzkaller.appspotmail.com
BUG: unable to handle kernel NULL pointer dereference at
#PF error: [INSTR]
PGD a7d75067 P4D a7d75067 PUD 9fa83067 PMD 0
Oops: 0010 [#1] PREEMPT SMP KASAN
CPU
On Thu, Feb 21, 2019 at 11:36:24AM -0800, Andrew Morton wrote:
> On Thu, 21 Feb 2019 06:52:04 -0800 syzbot
> wrote:
>
> > Hello,
> >
> > syzbot found the following crash on:
> >
> > HEAD commit:4aa9fc2a435a Revert "mm, memory_hotplug: initialize struct..
> > git tree: upstream
> >
On Thu, Feb 28, 2019 at 5:34 PM Jann Horn wrote:
>
> On Thu, Feb 28, 2019 at 1:57 PM Thomas Gleixner wrote:
> > On Thu, 28 Feb 2019, Jann Horn wrote:
> > > +Josh for unwinding, +x86 folks
> > > On Wed, Feb 27, 2019 at 11:43 PM Andrew Morton
> > > wrote:
> > > > On Thu, 21 Feb 2019 06:52:04
ic_perform_write() has two indirect calls:
>
> mapping->a_ops->write_begin() and ->write_end()
Does the indirect thunk thing really make any difference? When you
arrive at RIP=NULL, RSP points to a saved instruction pointer, just
like when indirect calls are compiled normally.
I ju
On Thu, 28 Feb 2019, Jann Horn wrote:
> +Josh for unwinding, +x86 folks
> On Wed, Feb 27, 2019 at 11:43 PM Andrew Morton
> wrote:
> > On Thu, 21 Feb 2019 06:52:04 -0800 syzbot
> > wrote:
> >
> > > Hello,
> > >
> > > syzbot found the following crash on:
> > >
> > > HEAD commit:4aa9fc2a435a
ved RIP but no saved RBP).
> > IMPORTANT: if you fix the bug, please add the following tag to the commit:
> > Reported-by: syzbot+ca95b2b7aef9e7cbd...@syzkaller.appspotmail.com
> >
> > BUG: unable to handle kernel NULL pointer dereference at
> > #PF error:
p.
> IMPORTANT: if you fix the bug, please add the following tag to the commit:
> Reported-by: syzbot+ca95b2b7aef9e7cbd...@syzkaller.appspotmail.com
>
> BUG: unable to handle kernel NULL pointer dereference at
> #PF error: [INSTR]
> PGD a7ea0067 P4D a7ea0067 P
yzbot+ca95b2b7aef9e7cbd...@syzkaller.appspotmail.com
BUG: unable to handle kernel NULL pointer dereference at
#PF error: [INSTR]
PGD a7ea0067 P4D a7ea0067 PUD 81535067 PMD 0
Oops: 0010 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 15924 Comm: syz-executor0 Not tainted 5.0.0-rc4+ #50
Hardware name: G
eatest stack depth: 11448 bytes left
> [ 274.120445] BUG: unable to handle kernel NULL pointer dereference
> at
> [ 274.128285] #PF error: [INSTR]
> [ 274.131351] PGD 800414a0e067 P4D 800414a0e067 PUD 3b6334067 PMD 0
> [ 274.138241] Oops: 0010 [#1] SM
kernel NULL pointer dereference
at
[ 274.128285] #PF error: [INSTR]
[ 274.131351] PGD 800414a0e067 P4D 800414a0e067 PUD 3b6334067 PMD 0
[ 274.138241] Oops: 0010 [#1] SMP PTI
[ 274.141734] CPU: 1 PID: 11464 Comm: ping Not tainted
5.0.0-rc4-next-20190129 #1
[ 274.149046
[7.742149] igt_debug total: 4096, used 2048 free 2048
[ 42.726577] [drm] Initialized vgem 1.0.0 20120112 for vgem on minor 0
[ 42.728241] Floppy drive(s): fd0 is 2.88M AMI BIOS
[ 42.729334] BUG: unable to handle kernel NULL pointer dereference at
[ 42.729735] #PF error: [normal
: using parport0 (interrupt-driven).
[ 19.266789] lp0: console ready
[ 19.294331] brd: module loaded
[ 19.303672] BUG: unable to handle kernel NULL pointer dereference at
[ 19.311670] #PF error: [normal kernel read fault]
[ 19.312646] *pdpt = *pde = f000ff53f000ff53
no device found
> [1.941848] nsc_gpio initializing
> [1.942249] Hangcheck: starting hangcheck timer 0.9.1 (tick is 180
> seconds, margin is 60 seconds).
> [1.943923] BUG: unable to handle kernel NULL pointer dereference at
> 0030
> [1.944889] #PF err
On Wed, Jan 2, 2019 at 4:51 PM Christopher Lameter wrote:
>
> On Wed, 2 Jan 2019, Dmitry Vyukov wrote:
>
> > Am I missing something or __alloc_alien_cache misses check for
> > kmalloc_node result?
> >
> > static struct alien_cache *__alloc_alien_cache(int node, int entries,
> >
On Wed, 2 Jan 2019, Dmitry Vyukov wrote:
> Am I missing something or __alloc_alien_cache misses check for
> kmalloc_node result?
>
> static struct alien_cache *__alloc_alien_cache(int node, int entries,
> int batch, gfp_t gfp)
> {
> size_t
che(>ac, entries, batch);
spin_lock_init(>lock);
return alc;
}
> BUG: unable to handle kernel NULL pointer dereference at 0038
> #PF error: [WRITE]
> PGD 8b2a5067 P4D 8b2a5067 PUD a53ed067 PMD 0
> Oops: 0002 [#1] PREEMPT SMP KASAN
> CPU: 1 PID: 16188
+d6ed4ec679652b4fd...@syzkaller.appspotmail.com
BUG: unable to handle kernel NULL pointer dereference at 0038
#PF error: [WRITE]
PGD 8b2a5067 P4D 8b2a5067 PUD a53ed067 PMD 0
Oops: 0002 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 16188 Comm: syz-executor4 Not tainted 4.20.0+ #174
Hardware name: Google
> device bridge_slave_0 left promiscuous mode
> bridge0: port 1(bridge_slave_0) entered disabled state
> team0 (unregistering): Port device team_slave_1 removed
> team0 (unregistering): Port device team_slave_0 removed
> bond0 (unregistering): Releasing backup interface bond_sla
000c42f90d718 R14: 00000066 R15: 00c42f90d708
> BUG: unable to handle kernel NULL pointer dereference at 0068
> PGD 1d85b1067 P4D 1d85b1067 PUD 1cd360067 PMD 0
> Oops: 0002 [#1] PREEMPT SMP KASAN
> CPU: 1 PID: 2748 Comm: syz-executor0 Not tainted 4.19.0-rc7+ #5
interface bond_slave_1
BUG: unable to handle kernel NULL pointer dereference at 00fc
PGD 1c38c3067 P4D 1c38c3067 PUD 1c38c8067 PMD 0
Oops: [#1] PREEMPT SMP KASAN
CPU: 1 PID: 5937 Comm: rs:main Q:Reg Not tainted 4.20.0-rc5+ #146
Hardware name: Google Google Compute Engine/Google
: 0001
R13: 00c42f90d718 R14: 0066 R15: 00c42f90d708
BUG: unable to handle kernel NULL pointer dereference at 0068
PGD 1d85b1067 P4D 1d85b1067 PUD 1cd360067 PMD 0
Oops: 0002 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 2748 Comm: syz-executor0 Not tainted 4.19.0-rc7+ #55
Hardware
em_u:system_r:kernel_t:s0
> tcontext=system_u:system_r:kernel_t:s0 tclass=memprotect permissive=1
> BUG: unable to handle kernel NULL pointer dereference at 0080
> PGD 0 P4D 0
> Oops: [#1] PREEMPT SMP KASAN
> CPU: 1 PID: 17455 Comm: udevd Not tainted 4.19.0+ #85
> Hardwa
; scontext=system_u:system_r:kernel_t:s0
tcontext=system_u:system_r:kernel_t:s0 tclass=memprotect permissive=1
BUG: unable to handle kernel NULL pointer dereference at 0080
PGD 0 P4D 0
Oops: [#1] PREEMPT SMP KASAN
CPU: 1 PID: 17455 Comm: udevd Not tainted 4.19.0+ #85
Hardware name: Goo
Ah, I got that. Thanks.
Kyungtae
Ah, I got that. Thanks.
Kyungtae
On Wed, Nov 21, 2018 at 11:11 AM, Kyungtae Kim wrote:
> Thank you for your reply.
> But I think this kind of crash can occur in real PC as well, and I'm
> just thinking of some way to stop it in the first place (if possible).
> because malicious users can use this, so as to make the whole system
On Wed, Nov 21, 2018 at 11:11 AM, Kyungtae Kim wrote:
> Thank you for your reply.
> But I think this kind of crash can occur in real PC as well, and I'm
> just thinking of some way to stop it in the first place (if possible).
> because malicious users can use this, so as to make the whole system
Thank you for your reply.
But I think this kind of crash can occur in real PC as well, and I'm
just thinking of some way to stop it in the first place (if possible).
because malicious users can use this, so as to make the whole system
(kernel) work incorrectly.
Thanks,
Kyungtae
Thank you for your reply.
But I think this kind of crash can occur in real PC as well, and I'm
just thinking of some way to stop it in the first place (if possible).
because malicious users can use this, so as to make the whole system
(kernel) work incorrectly.
Thanks,
Kyungtae
)
> To stop it, it probably needs a little tight bound check.
>
> I think this is a little bit related to the crash I reported before
> (https://lkml.org/lkml/2018/5/12/91)
>
> Crash log
> =============
> BUG: unable to handle kernel NULL pointer de
)
> To stop it, it probably needs a little tight bound check.
>
> I think this is a little bit related to the crash I reported before
> (https://lkml.org/lkml/2018/5/12/91)
>
> Crash log
> =============
> BUG: unable to handle kernel NULL pointer de
reported before
(https://lkml.org/lkml/2018/5/12/91)
Crash log
=
BUG: unable to handle kernel NULL pointer dereference at 00af
PGD 800092c1a067 P4D 800092c1a067 PUD 93a74067 PMD 0
Oops: 0002 [#1] SMP PTI
CPU: 0 PID: 6651 Comm: syz
1 - 100 of 1433 matches
Mail list logo
