[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20211027150429.ofg4vnwmnkj4aiky@intel.com>
Date: Wed, 27 Oct 2021 08:04:29 -0700
From: Ben Widawsky <ben.widawsky@...el.com>
To: YE Chengfeng <cyeaa@...nect.ust.hk>
Cc: "alison.schofield@...el.com" <alison.schofield@...el.com>,
"vishal.l.verma@...el.com" <vishal.l.verma@...el.com>,
"ira.weiny@...el.com" <ira.weiny@...el.com>,
"dan.j.williams@...el.com" <dan.j.williams@...el.com>,
"Jonathan.Cameron@...wei.com" <Jonathan.Cameron@...wei.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
linux-cxl@...r.kernel.org
Subject: Re: drivers/cxl: suspected null pointer dereference in core/bus.c
On 21-10-27 11:35:25, YE Chengfeng wrote:
> Hi,
>
> https://github.com/torvalds/linux/blob/master/drivers/cxl/core/bus.c#L98
>
> We notice that in multiple call sites, the return pointer of to_cxl_decoder is not null-checked, could it be a potential null-pointer-dereference problem?
>
> This is detected by our experimental static analysis tool, it could be false positive, we manually check and report those we think may be true issues. Would you like to have a look at them?
>
> Thanks so much,
> Chengfeng
add linux-cxl...
If NULL is returned, it's a driver bug. The WARN_ON and subsequent NULL deref
oops is desirable.
Powered by blists - more mailing lists