From: Du Cheng <ducheng2@gmail.com>
To: yildirim.fatih@gmail.com
Cc: gregkh@linuxfoundation.org, h.shahbazi.git@gmail.com,
linux-kernel@vger.kernel.org, Du Cheng <ducheng2@gmail.com>
Subject: [PATCH] drivers: tty: vt: vt.c: fix NULL dereference crash
Date: Fri, 12 Mar 2021 23:43:58 +0800 [thread overview]
Message-ID: <20210312154358.6941-1-ducheng2@gmail.com> (raw)
In-Reply-To: <14878df31817f11528c9326f2855819bcf782721.camel@gmail.com>
Hi Fatih,
I just found out that the section [Patch testing requests] on
https://syzkaller.appspot.com/bug?id=defb47bf56e1c14d5687280c7bb91ce7b608b94b,
indicates that you did not attach the patch when sending email to syzbot. syzbot
was simply testing the vallina upstream with repro.c, so it failed as expected.
Anyway, I resent the test email *with the patch* from Hassan to syzbot, and
let's see the result.
Regards,
Du Cheng
next prev parent reply other threads:[~2021-03-12 15:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-07 10:56 [PATCH] drivers: tty: vt: vt.c: fix NULL dereference crash Hassan Shahbazi
2021-03-12 8:33 ` Greg KH
2021-03-12 9:07 ` Fatih Yildirim
2021-03-12 15:43 ` Du Cheng [this message]
2021-03-13 9:12 ` Hassan Shahbazi
2021-03-12 15:05 ` Du Cheng
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=20210312154358.6941-1-ducheng2@gmail.com \
--to=ducheng2@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=h.shahbazi.git@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yildirim.fatih@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox