From: Jiri Slaby <jirislaby@gmail.com>
To: Valdis.Kletnieks@vt.edu
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
mm-commits@vger.kernel.org, linux-fsdevel@vger.kernel.org,
"H. Peter Anvin" <hpa@zytor.com>,
autofs@linux.kernel.org, npiggin@kernel.dk,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: WARNING: at fs/dcache.c:1359 d_set_d_op [was: mmotm 2011-01-06-15-41 uploaded]
Date: Thu, 13 Jan 2011 16:40:07 +0100 [thread overview]
Message-ID: <4D2F1CD7.5090100@gmail.com> (raw)
In-Reply-To: <12521.1294932824@localhost>
On 01/13/2011 04:33 PM, Valdis.Kletnieks@vt.edu wrote:
> On Thu, 13 Jan 2011 10:52:22 +0100, Jiri Slaby said:
>> On 01/07/2011 12:41 AM, akpm@linux-foundation.org wrote:
>>> The mm-of-the-moment snapshot 2011-01-06-15-41 has been uploaded to
>>
>> Hi, after some uptime and several suspend/resume cycles, I got:
>> WARNING: at fs/dcache.c:1359 d_set_d_op+0x82/0xb0()
>> Hardware name: To Be Filled By O.E.M.
>> Modules linked in: dvb_usb_af9015 tda18271 af9013 dvb_usb dvb_core
>> Pid: 3474, comm: automount Tainted: G W 2.6.37-mm1_64+ #1344
>> Call Trace:
>> [<ffffffff8106bd2a>] ? warn_slowpath_common+0x7a/0xb0
>> [<ffffffff8106bd75>] ? warn_slowpath_null+0x15/0x20
>> [<ffffffff81125a32>] ? d_set_d_op+0x82/0xb0
>> [<ffffffff8120d829>] ? autofs4_dir_mkdir+0x169/0x180
>
> Wow. So it wasn't just configfs that trips over this one. I'm now hoping that
> Al audited all the pseudo file systems for this...
Well, CCing Al.
I don't see any recent change in fs/autofs4 in:
http://git.kernel.org/?p=linux/kernel/git/viro/vfs-2.6.git;a=history;f=fs/autofs4;hb=refs/heads/for-next
So maybe not all?
regards,
--
js
next prev parent reply other threads:[~2011-01-13 15:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 23:41 mmotm 2011-01-06-15-41 uploaded akpm
2011-01-07 17:18 ` mmotm 2011-01-06-15-41 uploaded (apple_bl) Randy Dunlap
2011-01-13 9:52 ` WARNING: at fs/dcache.c:1359 d_set_d_op [was: mmotm 2011-01-06-15-41 uploaded] Jiri Slaby
2011-01-13 9:57 ` Jiri Slaby
2011-01-13 10:54 ` Nick Piggin
2011-01-13 15:33 ` Valdis.Kletnieks
2011-01-13 15:40 ` Jiri Slaby [this message]
2011-01-14 8:20 ` [autofs] " Ian Kent
2011-01-16 11:32 ` Jiri Slaby
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=4D2F1CD7.5090100@gmail.com \
--to=jirislaby@gmail.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=autofs@linux.kernel.org \
--cc=hpa@zytor.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=npiggin@kernel.dk \
--cc=viro@zeniv.linux.org.uk \
/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).