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:
or directory
# test failed: line value is 127 when 1 was expected
# GPIO gpio-mockup test FAIL
[ 124.539778] Unable to handle kernel NULL pointer dereference at
virtual address 05a8
[ 124.539864] Mem abort info:
[ 124.547998] ESR = 0x9606
[ 124.550188] EC = 0x25: DABT (current
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
> Arnd,
> I'm looking at the pl001_dma_probe(), I think we could make it more robust if
> it
> uses IS_ERR_OR_NULL(chan) instead of IS_ERR(). Should I send a patch for it? I
> suppose looking at the comment header for dma_request_chan() it does say
> return
> chan ptr or error ptr. Sorry I
On 7/6/2020 8:24 AM, Arnd Bergmann wrote:
On Mon, Jul 6, 2020 at 5:01 PM Dave Jiang wrote:
On 7/6/2020 5:53 AM, Arnd Bergmann wrote:
On Mon, Jul 6, 2020 at 1:03 PM Naresh Kamboju wrote:
Arnd,
I'm looking at the pl001_dma_probe(), I think we could make it more robust if it
uses
On Mon, Jul 6, 2020 at 5:01 PM Dave Jiang wrote:
> On 7/6/2020 5:53 AM, Arnd Bergmann wrote:
> > On Mon, Jul 6, 2020 at 1:03 PM Naresh Kamboju
> > wrote:
>
> Arnd,
> I'm looking at the pl001_dma_probe(), I think we could make it more robust if
> it
> uses IS_ERR_OR_NULL(chan) instead of
On 06-07-20, 07:33, Dave Jiang wrote:
> > I don't see anything suspicious in dmaengine drivers, but there is a
> > recent series
> > from Dave Jiang that might explain it. Could you try reverting commit
> > deb9541f5052 ("dmaengine: check device and channel list for empty")?
> >
> > I think the
,
[0.972053] Unable to handle kernel NULL pointer dereference at
virtual address
[0.975301] Mem abort info:
[0.976316] ESR = 0x9604
[0.977378] EC = 0x25: DABT (current EL), IL = 32 bits
[0.979363] SET = 0, FnV = 0
[0.980458] EA = 0, S1PTW = 0
,
[0.972053] Unable to handle kernel NULL pointer dereference at
virtual address
[0.975301] Mem abort info:
[0.976316] ESR = 0x9604
[0.977378] EC = 0x25: DABT (current EL), IL = 32 bits
[0.979363] SET = 0, FnV = 0
[0.980458] EA = 0, S1PTW = 0
arm64 boot crash log,
>
> [0.972053] Unable to handle kernel NULL pointer dereference at
> virtual address
> [0.975301] Mem abort info:
> [0.976316] ESR = 0x9604
> [0.977378] EC = 0x25: DABT (current EL), IL = 32 bits
> [0.979363]
: 5680d14d59bddc8bcbc5badf00dbbd4374858497
git describe: next-20200706
make_kernelversion: 5.8.0-rc3
kernel-config:
https://builds.tuxbuild.com/Glr-Ql1wbp3qN3cnHogyNA/kernel.config
qemu arm64 boot crash log,
[0.972053] Unable to handle kernel NULL pointer dereference at
virtual address
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
On Mon, 8 Apr 2019, Konstantin Khlebnikov wrote:
>
> I suppose your solution will wait for wakeup from shmem_evict_inode()?
No, it's the other way round: shmem_unuse() gets on with its work without
delay, shmem_evict_inode() waits until the stop_eviction count has gone
down to zero, saying
On 08.04.2019 9:05, Hugh Dickins wrote:
On Fri, 5 Apr 2019, Konstantin Khlebnikov wrote:
On 05.04.2019 5:12, Hugh Dickins wrote:
Hi Alex, could you please give the patch below a try? It fixes a
problem, but I'm not sure that it's your problem - please let us know.
I've not yet written up the
On Fri, 5 Apr 2019, Konstantin Khlebnikov wrote:
> On 05.04.2019 5:12, Hugh Dickins wrote:
> > Hi Alex, could you please give the patch below a try? It fixes a
> > problem, but I'm not sure that it's your problem - please let us know.
> >
> > I've not yet written up the commit description, and
from the BUG entry (I didn't bother to type it all,
low-quality image available upon request):
BUG: unable to handle kernel NULL pointer dereference at
#PF error: [normal kernel read fault]
PGD 0 P4D 0
Oops: [#1] SMP
CPU: 0 Comm: swapoff Not tainted 5.1.0-rc1+ #2
RIP: 0010
56a2d8af9147a4efe4011b60d93779c0461ca97, so CCing the related people.
> > > >>
> > > > Could you please provide more information on this - stack trace, dmesg
> > > > etc?
> > > > Is it easily reproducible? If yes, please detail the steps so that I
> &
se provide more information on this - stack trace, dmesg
> > > etc?
> > > Is it easily reproducible? If yes, please detail the steps so that I
> > > can try it inhouse.
> > >
> > > Thanks,
> > > Vineeth
> > >
> >
> > Some in
e steps so that I
> > can try it inhouse.
> >
> > Thanks,
> > Vineeth
> >
>
> Some info from the BUG entry (I didn't bother to type it all,
> low-quality image available upon request):
>
> BUG: unable to handle kernel NULL pointer dereference at 0
so CCing the related people.
>>
> Could you please provide more information on this - stack trace, dmesg etc?
> Is it easily reproducible? If yes, please detail the steps so that I
> can try it inhouse.
>
> Thanks,
> Vineeth
>
Some info from the BUG entry (I didn't bother to t
On Sun, Mar 24, 2019 at 11:30 AM Alex Xu (Hello71) wrote:
>
> I get this BUG in 5.1-rc1 sometimes when powering off the machine. I
> suspect my setup erroneously executes two swapoff+cryptsetup close
> operations simultaneously, so a race condition is triggered.
>
> I am using a single swap on a
I get this BUG in 5.1-rc1 sometimes when powering off the machine. I
suspect my setup erroneously executes two swapoff+cryptsetup close
operations simultaneously, so a race condition is triggered.
I am using a single swap on a plain dm-crypt device on a MBR partition
on a SATA drive.
I think
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
Hi,
My OS with V2.6.32 kernel capture an Oops:
2019-02-09T07:10:38.566968+08:00 nw-nhis1 kernel: [7972630.613854] BUG:
unable to handle kernel NULL pointer dereference at 00a8
2019-02-09T07:10:38.566992+08:00 nw-nhis1 kernel: [7972630.613859] IP:
[] next_tgid+0x5f/0x82
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
1 - 100 of 1596 matches
Mail list logo
