From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 88321] WARNING: CPU: 1 PID: 6784 at fs/dcache.c:1318 umount_check+0x77/0x7b()
Date: Sat, 02 Apr 2016 17:55:12 +0000 [thread overview]
Message-ID: <bug-88321-13602-UVbXZaOYop@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-88321-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=88321
Theodore Tso <tytso@mit.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tytso@mit.edu
--- Comment #2 from Theodore Tso <tytso@mit.edu> ---
Please note that Nick Krause was banned from the Linux Kernel list because he
has a tendency to guess, and while it was one thing to be wasting kernel
developers' time, it was quite another when he was giving bad advice to users
who were looking for help.
Having looked at the warning issued on line fs/dcache:1318, which is due to a
dentry in the file system to be unmounted was still being used. The
nfs_put_client() call has nothing to do with dentries.
If you want to try Nick's suggestion, please feel free. But it's not likely to
fix things, and it might make things worse.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2016-04-02 17:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-16 17:19 [Bug 88321] New: WARNING: CPU: 1 PID: 6784 at fs/dcache.c:1318 umount_check+0x77/0x7b() bugzilla-daemon
2016-04-02 15:56 ` [Bug 88321] " bugzilla-daemon
2016-04-02 17:55 ` bugzilla-daemon [this message]
2016-08-20 23:06 ` bugzilla-daemon
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=bug-88321-13602-UVbXZaOYop@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@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