From: Al Viro <viro@ftp.linux.org.uk>
To: Eddie Pettis <pettis.eddie@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How to locate struct file * from a bio?
Date: Wed, 31 Jan 2007 14:44:23 +0000 [thread overview]
Message-ID: <20070131144423.GB10050@ftp.linux.org.uk> (raw)
In-Reply-To: <d66e87630701310634s385db5adwa82e2194188efa81@mail.gmail.com>
On Wed, Jan 31, 2007 at 09:34:54AM -0500, Eddie Pettis wrote:
> Short question: Is it possible to locate the struct file * associated
> with a bio? If so, how?
Obviously impossible. For one thing, there might very well be no inode,
let alone struct file, associated with bio in question (e.g. for any
filesystem metadata). Moreover, the same on-disk object may get IO
without any stuct file at all (e.g. a directory) or with many struct
file (e.g. any file independently opened by several processes; no matter
how many of them do reads, we'll get stuff pulled into page cache the
same way (and once, not once per struct file).
next prev parent reply other threads:[~2007-01-31 14:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-31 14:34 How to locate struct file * from a bio? Eddie Pettis
2007-01-31 14:44 ` Al Viro [this message]
2007-01-31 14:51 ` Al Viro
2007-01-31 15:18 ` Helge Hafting
2007-01-31 18:45 ` Jan Engelhardt
2007-01-31 18:55 ` Eddie Pettis
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=20070131144423.GB10050@ftp.linux.org.uk \
--to=viro@ftp.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=pettis.eddie@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.