From: Dave Jiang <dave.jiang@intel.com>
To: Davidlohr Bueso <dave@stgolabs.net>
Cc: jonathan.cameron@huawei.com, alison.schofield@intel.com,
vishal.l.verma@intel.com, ira.weiny@intel.com,
dan.j.williams@intel.com, linux-cxl@vger.kernel.org
Subject: Re: [PATCH 0/2] cxl/mbox: fix undersized payload handling in cxl_payload_from_user_allowed()
Date: Fri, 20 Feb 2026 10:23:59 -0700 [thread overview]
Message-ID: <b981e259-ee48-43a8-96ff-bf7f46c71174@intel.com> (raw)
In-Reply-To: <20260220001618.963490-1-dave@stgolabs.net>
On 2/19/26 5:16 PM, Davidlohr Bueso wrote:
> Hi,
>
> The first patch fixes a KSAN splat uncovered by cxl fuzzying, the second
> is a follow up for maintain proper error code semantics.
>
> Applies against 'next' from cxl.git.
>
> Thanks!
>
> Davidlohr Bueso (2):
> cxl/mbox: validate payload size before accessing contents in cxl_payload_from_user_allowed()
> cxl/mbox: return appropriate error in cxl_payload_from_user_allowed()
>
> drivers/cxl/core/mbox.c | 31 ++++++++++++++++++++++---------
> 1 file changed, 22 insertions(+), 9 deletions(-)
>
> --
> 2.39.5
>
>
Reviewed-by: Dave Jiang <dave.jiang@intel.com>
for the series
prev parent reply other threads:[~2026-02-20 17:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-20 0:16 [PATCH 0/2] cxl/mbox: fix undersized payload handling in cxl_payload_from_user_allowed() Davidlohr Bueso
2026-02-20 0:16 ` [PATCH 1/2] cxl/mbox: validate payload size before accessing contents " Davidlohr Bueso
2026-02-23 19:23 ` Alison Schofield
2026-02-23 22:39 ` Dave Jiang
2026-02-20 0:16 ` [PATCH 2/2] cxl/mbox: return appropriate error " Davidlohr Bueso
2026-02-20 22:14 ` Alison Schofield
2026-02-21 18:55 ` Davidlohr Bueso
2026-02-23 19:27 ` Alison Schofield
2026-02-23 22:40 ` Dave Jiang
2026-02-27 13:38 ` Jonathan Cameron
2026-02-20 17:23 ` Dave Jiang [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=b981e259-ee48-43a8-96ff-bf7f46c71174@intel.com \
--to=dave.jiang@intel.com \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave@stgolabs.net \
--cc=ira.weiny@intel.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=vishal.l.verma@intel.com \
/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