[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <E1K3Ttv-0005ji-Cx@pomaz-ex.szeredi.hu>
Date: Tue, 03 Jun 2008 12:37:59 +0200
From: Miklos Szeredi <miklos@...redi.hu>
To: jesper@...gh.cc
CC: raven@...maw.net, viro@...IV.linux.org.uk, jesper@...gh.cc,
torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org
Subject: Re: Linux 2.6.26-rc4
> > > On Tue, Jun 03, 2008 at 11:49:32AM +0200, Jesper Krogh wrote:
> > >
> > >
> > >> I reported it to the NFS-guys on a .22 kernel, and was directed to the
> > >> fsdevel list(CC'ed again) back then. Now the problem is reproduced on
> > >> .26-rc4
> > >>
> > >
> > > Lovely... Do you have the full oops trace, with the actual code
> > > dump? --
> >
> > This is all I got from the logs. I'll try go get more from the serial
>
> Probably the same as this one:
>
> http://www.kerneloops.org/raw.php?rawid=12419&msgid=
>
> Looks like a negative inode in S_ISDIR(mnt->mnt_root->d_inode->i_mode),
> which would be due to NFS not properly filling in its root dentry?
On second thought it's S_ISDIR(path->dentry->d_inode->i_mode), which
means it's an autofs thing.
CC-ing Ian.
Miklos
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists