linux-kernel - Re: Re: Re: Re: [PATCH v3] serial: pch_uart: potential dereference of null pointer

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-Id: <20211217013129.423510-1-jiasheng@iscas.ac.cn>
Date:   Fri, 17 Dec 2021 09:31:29 +0800
From:   Jiasheng Jiang <jiasheng@...as.ac.cn>
To:     gregkh@...uxfoundation.org, jirislaby@...nel.org
Cc:     linux-serial@...r.kernel.org, linux-kernel@...r.kernel.org,
        Jiasheng Jiang <jiasheng@...as.ac.cn>
Subject: Re: Re: Re: Re: [PATCH v3] serial: pch_uart: potential dereference of null pointer

On Fri, Dec 17, 2021 at 00:14:28AM +0800, Greg KH wrote:
>> 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?

Er, I mean I have not got the technique to create the sitution that
the alloc would fail.
But it is universally accepted that the alloc would fail when the system
is under an extreme memory pressure.
If you insist to recurrent the bug, I will try my best to do it,
which I think it is needless.

Sincerely thanks,
jiasheng jiang