From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 66821] "BUG: soft lockup" in proc_fd_link, causing freeze
Date: Tue, 10 Dec 2013 21:20:40 +0000 [thread overview]
Message-ID: <bug-66821-13602-upRQgH8vzM@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-66821-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=66821
Theodore Tso <tytso@mit.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tytso@mit.edu
Component|Other |Other
Assignee|fs_ext4@kernel-bugs.osdl.or |fs_other@kernel-bugs.osdl.o
|g |rg
Product|Other |File System
--- Comment #2 from Theodore Tso <tytso@mit.edu> ---
proc_cwd_link and proc_fd_link are all procfs routines. So you have something
which is constantly scanning files in /proc?
In any case, it's highly unlikely this is an ext4 issues.
--
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2013-12-10 21:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-10 17:01 [Bug 66821] New: "BUG: soft lockup" in proc_fd_link, causing freeze bugzilla-daemon
2013-12-10 20:02 ` [Bug 66821] " bugzilla-daemon
2013-12-10 20:11 ` bugzilla-daemon
2013-12-10 21:20 ` bugzilla-daemon [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=bug-66821-13602-upRQgH8vzM@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