From: Greg KH <gregkh@linuxfoundation.org>
To: Jiasheng Jiang <jiasheng@iscas.ac.cn>
Cc: jirislaby@kernel.org, linux-serial@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Re: Re: [PATCH v3] serial: pch_uart: potential dereference of null pointer
Date: Thu, 16 Dec 2021 17:14:28 +0100 [thread overview]
Message-ID: <Ybtl5JUXKztUYqYz@kroah.com> (raw)
In-Reply-To: <20211216154113.423442-1-jiasheng@iscas.ac.cn>
On Thu, Dec 16, 2021 at 11:41:13PM +0800, Jiasheng Jiang wrote:
> On Thu, Dec 16, 2021 at 11:24:36PM +0800, Greg KH wrote:
> > Did you run the kernel before your change and then after your change to
> > ensure that the failure you saw before your change is now properly
> > fixed?
> >
> > How did you test this?
>
> Thank you for your answer. But I haven't run it yet.
> And in fact I don't know how to trigger the alloc failure.
Then perhaps this change is not needed?
thanks,
greg k-h
prev parent reply other threads:[~2021-12-16 16:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-16 15:41 Jiasheng Jiang
2021-12-16 16:14 ` Greg KH [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=Ybtl5JUXKztUYqYz@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jiasheng@iscas.ac.cn \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
/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®