From: Sergio Paracuellos <sparacuellos@lock-linux.com>
To: winter <winter.sui@gmail.com>
Cc: LINUX-Fs-DEVEL <linux-fsdevel@vger.kernel.org>
Subject: Re: Problems with current file descriptor
Date: Thu, 27 Oct 2005 09:20:06 +0200 [thread overview]
Message-ID: <1130397606.2864.4.camel@localhost.localdomain> (raw)
In-Reply-To: <16f1140f0510261934i51c53da1m@mail.gmail.com>
El jue, 27-10-2005 a las 10:34 +0800, winter escribió:
> 2005/10/26, Sergio Paracuellos <sparacuellos@lock-linux.com>:
> > Hi all,
> >
> > I have problems to know whats is the current file descriptor.
> >
> > "task_struct" have a files_struct structure which contains all files for
> > a process in "fd". If I want to get the complete path for one of them,
> > How can I know what is the correct one in fd_array?
> >
> > I suppose is something like:
> >
> > path = d_path(task->files->fd[x]->f_dentry,
> > task->files->fd[x]->f_vfsmnt, buf, PAGE_SIZE);
> >
> > But I don't know how to know this x for my correct file (for example the
> > last file I used).
> current file ?what is meaning?
> for exmaple ,you opened 3 file, file1,file2, file3. which is current file?
Sorry, I want the last file I used. For example if I just have done "cat
foobar" the file I want is this.
Thanks in advance,
> -
> To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2005-10-27 7:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-26 15:43 Problems with current file descriptor Sergio Paracuellos
2005-10-26 16:06 ` Jörn Engel
2005-10-27 2:34 ` winter
2005-10-27 7:20 ` Sergio Paracuellos [this message]
2005-10-27 8:30 ` winter
2005-10-27 9:06 ` Sergio Paracuellos
2005-10-27 9:26 ` Sergio Paracuellos
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=1130397606.2864.4.camel@localhost.localdomain \
--to=sparacuellos@lock-linux.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=winter.sui@gmail.com \
/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