From: Kirill Tkhai <ktkhai@virtuozzo.com>
To: David Howells <dhowells@redhat.com>, Al Viro <viro@zeniv.linux.org.uk>
Cc: David Rientjes <rientjes@google.com>,
linux-ia64@vger.kernel.org, avagin@virtuozzo.com,
peterz@infradead.org, heiko.carstens@de.ibm.com, hpa@zytor.com,
gorcunov@virtuozzo.com, linux-arch@vger.kernel.org,
linux-s390@vger.kernel.org, x86@kernel.org, mingo@redhat.com,
mattst88@gmail.com, fenghua.yu@intel.com, arnd@arndb.de,
ink@jurassic.park.msu.ru, tglx@linutronix.de, rth@twiddle.net,
tony.luck@intel.com, linux-kernel@vger.kernel.org,
linux-alpha@vger.kernel.org, schwidefsky@de.ibm.com,
davem@davemloft.net
Subject: Re: [PATCH 0/7] rwsem: Implement down_read_killable()
Date: Tue, 20 Jun 2017 13:36:50 +0300 [thread overview]
Message-ID: <20170620103648.vi7v45mjk63msw72@virtuozzo.com> (raw)
In-Reply-To: <2406.1497947414@warthog.procyon.org.uk>
On Tue, Jun 20, 2017 at 09:30, David Howells wrote:
> David Rientjes <rientjes@google.com> wrote:
>
> > I would have expected to see down_read_killable() actually used somewhere
> > after its implementation as part of this patchset.
>
> There are some places we should be using down_{read|write}_interruptible(), if
> it existed, dressed as inode_lock{,_shared}_interruptible().
Then let's use it in iterate_dir():
[PATCH]fs: Use killable down_read() in iterate_dir()
There was mutex_lock_interruptible() initially, and it was changed
to rwsem, but there were not killable rwsem primitives that time.
From commit 9902af79c01a:
"The main issue is the lack of down_write_killable(), so the places
like readdir.c switched to plain inode_lock(); once killable
variants of rwsem primitives appear, that'll be dealt with"
Use down_read_killable() same as down_write_killable() in !shared
case, as concurrent inode_lock() may take much time, that may be
wanted to be interrupted by user.
Signed-off-by: Kirill Tkhai <ktkhai@virtuozzo.com>
---
fs/readdir.c | 11 +++++------
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/fs/readdir.c b/fs/readdir.c
index 89659549c09d..7c584bbb4ce3 100644
--- a/fs/readdir.c
+++ b/fs/readdir.c
@@ -36,13 +36,12 @@ int iterate_dir(struct file *file, struct dir_context *ctx)
if (res)
goto out;
- if (shared) {
- inode_lock_shared(inode);
- } else {
+ if (shared)
+ res = down_read_killable(&inode->i_rwsem);
+ else
res = down_write_killable(&inode->i_rwsem);
- if (res)
- goto out;
- }
+ if (res)
+ goto out;
res = -ENOENT;
if (!IS_DEADDIR(inode)) {
prev parent reply other threads:[~2017-06-20 10:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170619180200.9jzmDGDBKZHdfFKf3iCHe7N7UhqaxG-FfpPV_v0g52U@z>
2017-06-19 18:02 ` [PATCH 0/7] rwsem: Implement down_read_killable() Kirill Tkhai
2017-06-19 18:02 ` [PATCH 1/7] rwsem-spinlock: Add killable versions of __down_read() Kirill Tkhai
2017-06-19 18:02 ` [PATCH 2/7] rwsem-spinlock: Add killable versions of rwsem_down_read_failed() Kirill Tkhai
2017-07-06 8:04 ` Peter Zijlstra
2017-07-06 9:45 ` Kirill Tkhai
2017-06-19 18:02 ` [PATCH 3/7] alpha: Add __down_read_killable() Kirill Tkhai
2017-06-19 18:02 ` [PATCH 4/7] ia64: " Kirill Tkhai
2017-06-19 18:03 ` [PATCH 5/7] s390: " Kirill Tkhai
2017-06-19 18:03 ` [PATCH 6/7] x86: " Kirill Tkhai
2017-06-19 18:03 ` [PATCH 7/7] rwsem: Add down_read_killable() Kirill Tkhai
2017-06-19 20:27 ` [PATCH 0/7] rwsem: Implement down_read_killable() David Rientjes
2017-06-20 8:30 ` David Howells
2017-06-20 10:36 ` Kirill Tkhai [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=20170620103648.vi7v45mjk63msw72@virtuozzo.com \
--to=ktkhai@virtuozzo.com \
--cc=arnd@arndb.de \
--cc=avagin@virtuozzo.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=fenghua.yu@intel.com \
--cc=gorcunov@virtuozzo.com \
--cc=heiko.carstens@de.ibm.com \
--cc=hpa@zytor.com \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mattst88@gmail.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rientjes@google.com \
--cc=rth@twiddle.net \
--cc=schwidefsky@de.ibm.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=viro@zeniv.linux.org.uk \
--cc=x86@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