On 01/13/2011 04:33 PM, [email protected] wrote: > On Thu, 13 Jan 2011 10:52:22 +0100, Jiri Slaby said: >> On 01/07/2011 12:41 AM, [email protected] 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 _______________________________________________ autofs mailing list [email protected] http://linux.kernel.org/mailman/listinfo/autofs
