linux-kernel - 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>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20211216154113.423442-1-jiasheng@iscas.ac.cn>
Date:   Thu, 16 Dec 2021 23:41:13 +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: [PATCH v3] serial: pch_uart: potential dereference of null pointer

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.
I just find the other place like eni_init_one() in `drivers/atm/eni.c`
check the return value of the dma_alloc_coherent().
So that's possible to alloc failure.
Therefore, in order to avoid the dereference of the null pointer, it might
be better to deal with it.

Sincerely thanks,

jiasheng jiang