From: syzbot <syzbot+be6ccf3081ce8afd1b56@syzkaller.appspotmail.com>
To: arve@android.com, christian@brauner.io,
devel@driverdev.osuosl.org, dja@axtens.net,
dri-devel@lists.freedesktop.org, dvyukov@google.com,
gregkh@linuxfoundation.org, joel@joelfernandes.org,
kasan-dev@googlegroups.com, labbott@redhat.com,
linaro-mm-sig-owner@lists.linaro.org,
linaro-mm-sig@lists.linaro.org, linux-kernel@vger.kernel.org,
maco@android.com, sumit.semwal@linaro.org,
syzkaller-bugs@googlegroups.com, tkjos@android.com
Subject: Re: BUG: unable to handle kernel paging request in ion_heap_clear_pages
Date: Fri, 28 Feb 2020 00:02:11 -0800 [thread overview]
Message-ID: <0000000000003eeb63059f9e41d2@google.com> (raw)
In-Reply-To: <00000000000080f1d305988bb8ba@google.com>
This bug is marked as fixed by commit:
kasan: support vmalloc backing of vm_map_ram()
But I can't find it in any tested tree for more than 90 days.
Is it a correct commit? Please update it by replying:
#syz fix: exact-commit-title
Until then the bug is still considered open and
new crashes with the same signature are ignored.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: syzbot <syzbot+be6ccf3081ce8afd1b56@syzkaller.appspotmail.com>
To: arve@android.com, christian@brauner.io,
devel@driverdev.osuosl.org, dja@axtens.net,
dri-devel@lists.freedesktop.org, dvyukov@google.com,
gregkh@linuxfoundation.org, joel@joelfernandes.org,
kasan-dev@googlegroups.com, labbott@redhat.com,
linaro-mm-sig-owner@lists.linaro.org,
linaro-mm-sig@lists.linaro.org, linux-kernel@vger.kernel.org,
maco@android.com, sumit.semwal@linaro.org,
syzkaller-bugs@googlegroups.com, tkjos@android.com
Subject: Re: BUG: unable to handle kernel paging request in ion_heap_clear_pages
Date: Fri, 28 Feb 2020 00:02:11 -0800 [thread overview]
Message-ID: <0000000000003eeb63059f9e41d2@google.com> (raw)
In-Reply-To: <00000000000080f1d305988bb8ba@google.com>
This bug is marked as fixed by commit:
kasan: support vmalloc backing of vm_map_ram()
But I can't find it in any tested tree for more than 90 days.
Is it a correct commit? Please update it by replying:
#syz fix: exact-commit-title
Until then the bug is still considered open and
new crashes with the same signature are ignored.
next prev parent reply other threads:[~2020-02-29 10:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-30 7:59 BUG: unable to handle kernel paging request in ion_heap_clear_pages syzbot
2019-11-30 7:59 ` syzbot
2019-11-30 8:01 ` Dmitry Vyukov
2019-11-30 8:01 ` Dmitry Vyukov
2019-12-03 15:52 ` syzbot
2019-12-03 15:52 ` syzbot
2020-02-28 8:02 ` syzbot [this message]
2020-02-28 8:02 ` syzbot
2020-03-01 22:56 ` Daniel Axtens
2020-03-01 22:56 ` Daniel Axtens
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=0000000000003eeb63059f9e41d2@google.com \
--to=syzbot+be6ccf3081ce8afd1b56@syzkaller.appspotmail.com \
--cc=arve@android.com \
--cc=christian@brauner.io \
--cc=devel@driverdev.osuosl.org \
--cc=dja@axtens.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=dvyukov@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=joel@joelfernandes.org \
--cc=kasan-dev@googlegroups.com \
--cc=labbott@redhat.com \
--cc=linaro-mm-sig-owner@lists.linaro.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maco@android.com \
--cc=sumit.semwal@linaro.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tkjos@android.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.