From: Matthew Wilcox <willy@infradead.org>
To: Olga Kornievskaia <aglo@umich.edu>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: is this hang in a rename syscall is known?
Date: Thu, 9 Apr 2020 11:51:32 -0700 [thread overview]
Message-ID: <20200409185132.GY21484@bombadil.infradead.org> (raw)
In-Reply-To: <CAN-5tyF9JX1VaevFcvDKAcHa1XTgYznOMwW+LMigA-awqn_m7w@mail.gmail.com>
On Thu, Apr 09, 2020 at 12:44:25PM -0400, Olga Kornievskaia wrote:
> Hi folks,
>
> Getting this hang on a 5.5 kernel, is this a known issue? Thank you.
I haven't seen it reported.
> Apr 7 13:34:53 scspr1865142002 kernel: Not tainted 5.5.7 #1
> Apr 7 13:34:53 scspr1865142002 kernel: "echo 0 >
> /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> Apr 7 13:34:53 scspr1865142002 kernel: dt D 0 24788
> 24323 0x00000080
> Apr 7 13:34:53 scspr1865142002 kernel: Call Trace:
> Apr 7 13:34:53 scspr1865142002 kernel: ? __schedule+0x2ca/0x6e0
> Apr 7 13:34:53 scspr1865142002 kernel: schedule+0x4a/0xb0
> Apr 7 13:34:53 scspr1865142002 kernel: schedule_preempt_disabled+0xa/0x10
> Apr 7 13:34:53 scspr1865142002 kernel: __mutex_lock.isra.11+0x233/0x4e0
> Apr 7 13:34:53 scspr1865142002 kernel: ? strncpy_from_user+0x47/0x160
> Apr 7 13:34:53 scspr1865142002 kernel: lock_rename+0x28/0xd0
This task is doing a cross-directory rename() operation. We only allow
one of those in progress per filesystem at any given time (because they're
quite rare and rearranging the tree like that plays merry havoc with the
locking, which you need to prevent a directory becoming its own ancestor).
So the question is, who else is in the middle of a rename operation and
has blocked for a long time while holding the s_vfs_rename_mutex?
As I recall, you work on NFS, so has something weird been going on with
your network?
next prev parent reply other threads:[~2020-04-09 18:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-09 16:44 is this hang in a rename syscall is known? Olga Kornievskaia
2020-04-09 18:51 ` Matthew Wilcox [this message]
2020-04-09 19:30 ` Olga Kornievskaia
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=20200409185132.GY21484@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=aglo@umich.edu \
--cc=linux-fsdevel@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).