From: "Mohit Katiyar" <katiyar.mohit@gmail.com>
To: linux-fsdevel@vger.kernel.org
Subject: Getattr calls
Date: Fri, 13 Oct 2006 18:53:21 +0900 [thread overview]
Message-ID: <46465bb30610130253s70329a74m4bc58c78a8ca7b7e@mail.gmail.com> (raw)
Hi,
I have just shifted from using linux-2.6.5 to 2.6.16 and I am seeing a
change in mounting operation.
I have created a dummy file-system, put some printk in getattr method
of this file system.
Using 2.6.16 kernel I do the following steps
1) First I mount my dummy filesystem
mount -t rkfs none ../rkfs/rkfsmnt
2) Then I mounted a partition from different machine though nfs.
mount -t nfs 10.112.4.168:/home/guest /mnt/nfs
Now /var/log/messages show that rkfs(dummy filesystem) getattr has
been called while mounting the nfs partition.
Is it a normal behaviour??
If it is then why it does not happen in 2.6.5 kernel?
Can anyone help me find out where and in which part of the kernel the
changes has been made to show such behaviour??
TIA
Mohit Katiyar
reply other threads:[~2006-10-13 9:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=46465bb30610130253s70329a74m4bc58c78a8ca7b7e@mail.gmail.com \
--to=katiyar.mohit@gmail.com \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).