From: Sasha Levin <sashal@kernel.org>
To: Dan Williams <dan.j.williams@intel.com>
Cc: stable@vger.kernel.org, Vishal Verma <vishal.l.verma@intel.com>
Subject: Re: [5.2-stable PATCH 1/2] libnvdimm/bus: Prepare the nd_ioctl() path to be re-entrant
Date: Tue, 6 Aug 2019 18:18:43 -0400 [thread overview]
Message-ID: <20190806221843.GP17747@sasha-vm> (raw)
In-Reply-To: <156505494437.1043830.9239219668937125315.stgit@dwillia2-desk3.amr.corp.intel.com>
On Mon, Aug 05, 2019 at 06:29:04PM -0700, Dan Williams wrote:
>commit 6de5d06e657acdbcf9637dac37916a4a5309e0f4 upstream.
>
>In preparation for not holding a lock over the execution of nd_ioctl(),
>update the implementation to allow multiple threads to be attempting
>ioctls at the same time. The bus lock still prevents multiple in-flight
>->ndctl() invocations from corrupting each other's state, but static
>global staging buffers are moved to the heap.
>
>Reported-by: Vishal Verma <vishal.l.verma@intel.com>
>Reviewed-by: Vishal Verma <vishal.l.verma@intel.com>
>Tested-by: Vishal Verma <vishal.l.verma@intel.com>
>Link: https://lore.kernel.org/r/156341208947.292348.10560140326807607481.stgit@dwillia2-desk3.amr.corp.intel.com
>Signed-off-by: Dan Williams <dan.j.williams@intel.com>
I've queued up both the 5.2 and 4.19 patches, thanks!
--
Thanks,
Sasha
prev parent reply other threads:[~2019-08-06 22:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 1:29 [5.2-stable PATCH 1/2] libnvdimm/bus: Prepare the nd_ioctl() path to be re-entrant Dan Williams
2019-08-06 1:29 ` [5.2-stable PATCH 2/2] libnvdimm/bus: Fix wait_nvdimm_bus_probe_idle() ABBA deadlock Dan Williams
2019-08-06 22:18 ` Sasha Levin [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=20190806221843.GP17747@sasha-vm \
--to=sashal@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=stable@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