From: Anton Altaparmakov <aia21@cam.ac.uk>
To: "Kathy KN (HK)" <kathy.kn@gmail.com>
Cc: Jeff Mahoney <jeffm@suse.com>, linux-fsdevel@vger.kernel.org
Subject: Re: Access content of file via inodes
Date: Fri, 08 Apr 2005 09:17:59 +0100 [thread overview]
Message-ID: <1112948279.28245.4.camel@imp.csi.cam.ac.uk> (raw)
In-Reply-To: <f8ad67b305040723012246f254@mail.gmail.com>
On Fri, 2005-04-08 at 14:01 +0800, Kathy KN (HK) wrote:
> On Apr 6, 2005 3:01 AM, Jeff Mahoney <jeffm@suse.com> wrote:
> > Kathy KN wrote:
> > > Good day all,
> > >
> > > How do I access/read the content of the files via using inodes
> > > or blocks that belong to the inode, at sys_link and vfs_link layer?
> > > I used bmap to access the blocks that belongs to the inodes, but
> > > getting access to the buffer_head's b_data doesn't seem to help.
> >
> > Hi Kathy -
> >
> > What you're trying to do is possible, but you need to go about it in a
> > different way. Ignore the buffer cache completely and use the page
> > cache; it's more appropriate for file contents.
> >
> > You have two options:
> >
> > If performance isn't critical, a simple approach would be to use your
> > old_dentry pointer to dentry_open a file and then vfs_read from it to a
> > buffer you allocate. Make sure you use get_fs/set_fs, since vfs_read
> > won't accept a kernel pointer otherwise.
> >
> > If performance is more important or you really do only have access to an
> > inode, you can read from the page cache directly using inode->i_mapping
> > and read_cache_page. This has the advantage that you don't need to copy
> > the data to access it, but the disadvantage that it is more complex and
> > can be tricky to get right.
>
> Hi Jeff,
>
> Is it possible to modify the cached page, and invalidate it back
> to update the page cache of the new page? I did a recursive grep
> and could only find functions that let you read or grab pages in the
> cache.
Once you have the page (via read_cache_page() or whatever) you can
simply write to it, then do a flush_dcache_page(page), then
set_page_dirty(page) and finally do the page_cache_release(). Oh, and
don't forget to unmap the page. Usually done straight after the
flush_dcache_page(). And example from ntfs where we get a page, memset
it to a value (val), and then mark it dirty for later write out:
page = read_cache_page(mapping, idx,
(filler_t*)mapping->a_ops->readpage, NULL);
if (IS_ERR(page)) {
ntfs_error(vol->sb, "Failed to read first partial "
"page (sync error, index 0x%lx).", idx);
return PTR_ERR(page);
}
wait_on_page_locked(page);
if (unlikely(!PageUptodate(page))) {
ntfs_error(vol->sb, "Failed to read first partial page "
"(async error, index 0x%lx).", idx);
page_cache_release(page);
return PTR_ERR(page);
}
size = PAGE_CACHE_SIZE;
if (idx == end)
size = end_ofs;
kaddr = kmap_atomic(page, KM_USER0);
memset(kaddr + start_ofs, val, size - start_ofs);
flush_dcache_page(page);
kunmap_atomic(kaddr, KM_USER0);
set_page_dirty(page);
page_cache_release(page);
Of course you need to serialise access in some way so multiple writers
do not step on each other's toes, etc...
Best regards,
Anton
--
Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)
Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK
Linux NTFS maintainer / IRC: #ntfs on irc.freenode.net
WWW: http://linux-ntfs.sf.net/ & http://www-stu.christs.cam.ac.uk/~aia21/
next prev parent reply other threads:[~2005-04-08 8:18 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-05 1:23 Access content of file via inodes Kathy KN
2005-04-05 7:22 ` Christoph Hellwig
2005-04-05 17:53 ` Bryan Henderson
2005-04-06 1:27 ` Kathy KN (HK)
2005-04-06 1:53 ` Jeff Mahoney
2005-04-06 17:57 ` Bryan Henderson
2005-04-06 7:54 ` Anton Altaparmakov
2005-04-06 11:33 ` Anton Altaparmakov
2005-04-06 13:09 ` Jeffrey Mahoney
2005-04-07 5:25 ` Kathy KN (HK)
2005-04-07 6:47 ` Jeffrey Mahoney
2005-04-07 8:09 ` Anton Altaparmakov
2005-04-05 19:01 ` Jeff Mahoney
2005-04-06 1:32 ` Kathy KN (HK)
2005-04-06 1:50 ` Jeff Mahoney
2005-04-08 6:01 ` Kathy KN (HK)
2005-04-08 8:17 ` Anton Altaparmakov [this message]
2005-05-27 19:13 ` Martin Jambor
2005-05-28 15:57 ` Anton Altaparmakov
2005-05-28 21:44 ` Martin Jambor
2005-05-29 7:26 ` Anton Altaparmakov
2005-05-30 21:51 ` Martin Jambor
2005-05-30 22:19 ` Anton Altaparmakov
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=1112948279.28245.4.camel@imp.csi.cam.ac.uk \
--to=aia21@cam.ac.uk \
--cc=jeffm@suse.com \
--cc=kathy.kn@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).