archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <>
To: Ben Widawsky <>
	linux-nvdimm <>,
	Alison Schofield <>,
	Al Viro <>,
	Konrad Rzeszutek Wilk <>,
	Jonathan Cameron <>
Subject: Re: [PATCH] cxl/mem: Fixes to IOCTL interface
Date: Sat, 20 Feb 2021 18:38:36 -0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Sat, Feb 20, 2021 at 1:57 PM Ben Widawsky <> wrote:
> When submitting a command for userspace, input and output payload bounce
> buffers are allocated. For a given command, both input and output
> buffers may exist and so when allocation of the input buffer fails, the
> output buffer must be freed. As far as I can tell, userspace can't
> easily exploit the leak to OOM a machine unless the machine was already
> near OOM state.
> This bug was introduced in v5 of the patch and did not exist in prior
> revisions.

Thanks for the quick turnaround, but I think that speed introduced
some issues...

> While here, adjust the variable 'j' found in patch review by Konrad.

Please split this pure cleanup to its own patch. The subject says
"Fixes", but it's only the one fix.

> Cc: Al Viro <>
> Reported-by: Konrad Rzeszutek Wilk <>

Since the commit is upstream add a "Fixes" line:

Fixes: 583fa5e71cae ('cxl/mem: Add basic IOCTL interface")

> Signed-off-by: Ben Widawsky <>
> Reviewed-by: Dan Williams <> (v2)
> Reviewed-by: Jonathan Cameron <>

Jonathan and I didn't pre-review this.
Linux-nvdimm mailing list --
To unsubscribe send an email to

  reply	other threads:[~2021-02-21  2:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-20 21:56 [PATCH] cxl/mem: Fixes to IOCTL interface Ben Widawsky
2021-02-21  2:38 ` Dan Williams [this message]
2021-02-21  3:47   ` Ben Widawsky
2021-02-22 16:12     ` Dan Williams
2021-02-22 17:19     ` Konrad Rzeszutek Wilk
2021-02-21  3:58 ` [PATCH v2] cxl/mem: Fix potential memory leak Ben Widawsky
2021-02-22 16:28   ` Jonathan Cameron
2021-02-22 17:09   ` Konrad Rzeszutek Wilk

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).