From: Ben Widawsky <ben.widawsky@intel.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: linux-cxl@vger.kernel.org
Subject: Re: [PATCH] cxl/core: Fix cxl_device_lock() class detection
Date: Wed, 9 Feb 2022 09:39:29 -0800 [thread overview]
Message-ID: <20220209173929.ivkvmf6nr4omrqwc@intel.com> (raw)
In-Reply-To: <164439225406.2941117.3927102269866914339.stgit@dwillia2-desk3.amr.corp.intel.com>
On 22-02-08 23:37:34, Dan Williams wrote:
> If cxl_device_lock() is used on a non-CXL device the expectation is that
> the lock class will fall back to CXL_ANON_LOCK. Instead it crashes when
> trying to determine if the device is a 'decoder'. Specifically when the
> device has a NULL type pointer. Just check for NULL before
> de-referencing ->release.
>
> Fixes: 3c5b90395525 ("cxl: Prove CXL locking")
> Reported-by: Ben Widawsky <ben.widawsky@intel.com>
> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Reviewed-by: Ben Widawsky <ben.widawsky@intel.com>
> ---
> drivers/cxl/core/port.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/cxl/core/port.c b/drivers/cxl/core/port.c
> index 9b4bbd51fbaa..d29eb2abdbc2 100644
> --- a/drivers/cxl/core/port.c
> +++ b/drivers/cxl/core/port.c
> @@ -284,7 +284,7 @@ EXPORT_SYMBOL_NS_GPL(is_root_decoder, CXL);
>
> bool is_cxl_decoder(struct device *dev)
> {
> - return dev->type->release == cxl_decoder_release;
> + return dev->type && dev->type->release == cxl_decoder_release;
> }
> EXPORT_SYMBOL_NS_GPL(is_cxl_decoder, CXL);
>
>
prev parent reply other threads:[~2022-02-09 17:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 7:37 [PATCH] cxl/core: Fix cxl_device_lock() class detection Dan Williams
2022-02-09 17:39 ` Ben Widawsky [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=20220209173929.ivkvmf6nr4omrqwc@intel.com \
--to=ben.widawsky@intel.com \
--cc=dan.j.williams@intel.com \
--cc=linux-cxl@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