From: "Bryant G. Ly" <bryantly@linux.vnet.ibm.com>
To: Christoph Hellwig <hch@lst.de>,
"Nicholas A. Bellinger" <nab@linux-iscsi.org>
Cc: target-devel <target-devel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
Joel Becker <jlbec@evilplan.org>
Subject: Re: [PATCH] configfs: Fix race between create_link and configfs_rmdir
Date: Thu, 8 Jun 2017 07:34:05 -0500 [thread overview]
Message-ID: <c76cb2bd-726b-7334-ae74-f2870390efb6@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170608072129.GA13433@lst.de>
> Thanks Nic,
>
> applied to the configfs-for-next tree. I'm not entirely sure if we
> should bother adding this to 4.12 or if it hits rarely enough?
>
It hits for us pretty often when we have a GPFS setup with 10 hosts and 1k+ vms.
That is how we discovered the bug in the first place.
-Bryant
next prev parent reply other threads:[~2017-06-08 12:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 4:51 [PATCH] configfs: Fix race between create_link and configfs_rmdir Nicholas A. Bellinger
2017-06-08 7:21 ` Christoph Hellwig
2017-06-08 12:34 ` Bryant G. Ly [this message]
2017-06-09 7:05 ` Nicholas A. Bellinger
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=c76cb2bd-726b-7334-ae74-f2870390efb6@linux.vnet.ibm.com \
--to=bryantly@linux.vnet.ibm.com \
--cc=hch@lst.de \
--cc=jlbec@evilplan.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=nab@linux-iscsi.org \
--cc=target-devel@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;
as well as URLs for NNTP newsgroup(s).