From: Dmitry Vyukov <dvyukov@google.com>
To: wchenbt@cse.ust.hk
Cc: LKML <linux-kernel@vger.kernel.org>,
syzkaller <syzkaller@googlegroups.com>
Subject: Re: KASAN: use-after-free Read in screen_glyph_unicode
Date: Tue, 14 Jan 2020 07:38:05 +0100 [thread overview]
Message-ID: <CACT4Y+a4LPFvu6Dx6PoS-5efmSqKCuXQTK+F9SP+X8U8VdeOFQ@mail.gmail.com> (raw)
In-Reply-To: <8645e64d639e9213bf68d0fdbee0c297.squirrel@imail.cse.ust.hk>
Hi Wei,
You should add relevant kernel maintainers to CC list when reporting
kernel bugs, nobody is generally reading LKML mailing list. Please
see:
https://github.com/google/syzkaller/blob/master/docs/linux/reporting_kernel_bugs.md
or any other kernel bug reporting guide.
On Tue, Jan 14, 2020 at 7:33 AM <wchenbt@cse.ust.hk> wrote:
>
> Dear Linux kernel developers,
>
> I found the crash “KASAN: use-after-free Read in screen_glyph_unicode”
> when running syzkaller, hope it’s unknown:
>
> Linux version: 1c163f4c7b3f Linux 5.0
> Branch: KASAN: use-after-free in screen_glyph drivers/tty/vt/vt.c:4566
>
> Please get rhe C repo and crash log generated by syzkaller from google
> drive https://drive.google.com/drive/folders/1zolqAlgnweSbr2-OzFFH2Neot4RGMBiV?usp=sharing,
> as well as the .config I used for linux kernel from the attachment.
> Thanks.
>
> Thanks,
> Wei
>
> --
> You received this message because you are subscribed to the Google Groups "syzkaller" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller+unsubscribe@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller/8645e64d639e9213bf68d0fdbee0c297.squirrel%40imail.cse.ust.hk.
prev parent reply other threads:[~2020-01-14 6:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 6:33 wchenbt
2020-01-14 6:38 ` Dmitry Vyukov [this message]
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+a4LPFvu6Dx6PoS-5efmSqKCuXQTK+F9SP+X8U8VdeOFQ@mail.gmail.com \
--to=dvyukov@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller@googlegroups.com \
--cc=wchenbt@cse.ust.hk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®