Re: linux-next: Tree for Feb 23 [ fs/dcache.c: Root dentry has weirdname <SYSV00000000> ]

[Sedat Dilek]

On Mon, Feb 25, 2013 at 6:00 AM, Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> wrote:
> Hi all,
>
> Please do not add any work destined for v3.10 to your -next included
> branches until after Linus has release v3.9-rc1.
>
> Changes since 20130222:
>
> The metag tree gained a conflict against Linus' tree.
>
> The kbuild tree gained a build failure so I used the version from
> next-20130222.
>
> The drm tree still has its build failure for which I applied a patch.
>
> The watchdog tree gained a conflict against Linus' tree.
>
> The akpm tree gained a conflict against the vfs tree and lost lots of
> patches that turned up elsewhere.
>
> ----------------------------------------------------------------------------
>

[ CCing linux-fsdevel and Al ]

Hi,

with today's Linux-Next (next-20130225) I get the following call-trace:

[  120.310366] Root dentry has weird name <SYSV00000000>
[  120.310367] Modules linked in: snd_hda_codec_hdmi
snd_hda_codec_realtek bnep coretemp rfcomm kvm_intel arc4 kvm iwldvm
ghash_clmulni_intel parport_pc aesni_intel mac80211 ppdev xts
snd_hda_intel aes_x86_64 uvcvideo snd_hda_codec lrw gf128mul snd_hwdep
ablk_helper i915 videobuf2_vmalloc snd_pcm cryptd joydev
videobuf2_memops videobuf2_core snd_page_alloc videodev snd_seq_midi
iwlwifi snd_seq_midi_event snd_rawmidi i2c_algo_bit snd_seq
drm_kms_helper snd_timer psmouse drm snd_seq_device cfg80211 btusb
microcode snd serio_raw bluetooth soundcore lpc_ich samsung_laptop wmi
mei mac_hid video lp parport r8169
[  120.310406] Pid: 2304, comm: firefox Tainted: G      D
3.8.0-next20130225-1-iniza-small #1
[  120.310408] Call Trace:
[  120.310414]  [<ffffffff8105a6af>] warn_slowpath_common+0x7f/0xc0
[  120.310417]  [<ffffffff8105a7a6>] warn_slowpath_fmt+0x46/0x50
[  120.310419]  [<ffffffff811ab954>] prepend_path+0x204/0x210
[  120.310422]  [<ffffffff811accaa>] d_path+0xda/0x150
[  120.310426]  [<ffffffff811b9721>] seq_path+0x51/0xd0
[  120.310430]  [<ffffffff811fa71b>] show_map_vma+0x15b/0x290
[  120.310432]  [<ffffffff811fa901>] show_pid_map+0x31/0x80
[  120.310435]  [<ffffffff811b9546>] seq_read+0x256/0x3e0
[  120.310438]  [<ffffffff81197150>] vfs_read+0xb0/0x180
[  120.310440]  [<ffffffff81197272>] sys_read+0x52/0xa0
[  120.310444]  [<ffffffff816cc61d>] system_call_fastpath+0x1a/0x1f
[  120.310446] ---[ end trace 941ac4690a5baea1 ]---

Can't say what caused it right now.
Did not check MLs if this is known and/or a fix around.

My kernel-config is attached!

Regards,
- Sedat -

Attachment: config-3.8.0-next20130225-1-iniza-small
Description: Binary data