From: "Vladimir V. Saveliev" <vs@namesys.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, Christoph Hellwig <hch@lst.de>
Subject: Re: bug in get_name of export operations?
Date: Tue, 20 Dec 2005 14:35:03 +0300 [thread overview]
Message-ID: <43A7EC67.5030400@namesys.com> (raw)
In-Reply-To: <20051220025209.df6d5c81.akpm@osdl.org>
Hello
Andrew Morton wrote:
> "Vladimir V. Saveliev" <vs@namesys.com> wrote:
>>Hello
>>
>>Please point my error if I am wrong:
>>
>>fs/exportfs/expfs.c:get_name() opens a directory with:
>>file = dentry_open(dget(dentry), NULL, O_RDONLY);
>>which results in file where file->f_vfsmnt == NULL.
>>
>>Then fs/readdir.c:vfs_readdir() and, therefore,
>>include/linux/fs.h:file_accessed(file) are called.
>>file_accessed() calls fs/inode.c:touch_atime() which tryies to dereference mnt
>>which is NULL.
>>
>
> I think you're looking at the -mm tree, in which Christoph changed all that
> stuff.
>
Ah, sorry, yes, I found that in 2.6.15-rc5-mm3
prev parent reply other threads:[~2005-12-20 11:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-19 14:56 bug in get_name of export operations? Vladimir V. Saveliev
2005-12-20 10:52 ` Andrew Morton
2005-12-20 11:35 ` Vladimir V. Saveliev [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=43A7EC67.5030400@namesys.com \
--to=vs@namesys.com \
--cc=akpm@osdl.org \
--cc=hch@lst.de \
--cc=linux-kernel@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