From: " ÀÌÈ£ " <i@flyduck.com>
To: "Blesson Paul" <blessonpaul@usa.net>, <linux-kernel@vger.kernel.org>
Subject: Re: [Re: __asm__ ]
Date: Wed, 23 May 2001 18:33:28 +0900 [thread overview]
Message-ID: <026201c0e36b$6d10d780$2502a8c0@flyduck.flyduck.com> (raw)
Blesson Paul Wrote:
> Thanks for the reply. I am sorry that I misspelled the
> line(__asm__(....)). It is from the get_current() function in
> asm-i386/current.h. But I am not clear what is the whole meaning of that
> line(__asm__(..)) in get_current(). I am doing a project in Linux related to
> VFS. From VFS. this function is called to get the base of the file system. I
> am not getting how this function will gave the base of the file system.
> get_current() is called from lookup_dentry function.
> base=dget(current->fs->root)
get_current() returns the pointer to process descriptor
(struct task_struct). Kernel allocates 8KB per each process,
which is used for the process descriptor of process, and
process kernel stack. So masking out 13 LSB of stack
poiniter yields the pointer to process descriptor.
You can find more explanation in the Chapter 3 of
<Understanding the Linux Kernel>
fs field in the process descriptor describes the root directory
and the current working directory of the process. so
current->fs->root is the pointer to the directory entry of
process' root directory.
*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*
Lee, Ho. Software Engineer, Embedded Linux Dep, LinuxOne
ICQ : #52017992, Mail : flyduck@linuxone.co.kr, i@flyduck.com
Homepage : http://flyduck.com, http://linuxkernel.to
next reply other threads:[~2001-05-23 9:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-23 9:33 ÀÌÈ£ [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-23 9:00 [Re: __asm__ ] Blesson Paul
2001-05-23 10:50 ` David Howells
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='026201c0e36b$6d10d780$2502a8c0@flyduck.flyduck.com' \
--to=i@flyduck.com \
--cc=blessonpaul@usa.net \
--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