[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <812200.1627292675@warthog.procyon.org.uk>
Date: Mon, 26 Jul 2021 10:44:35 +0100
From: David Howells <dhowells@...hat.com>
To: Jeff Layton <jlayton@...hat.com>
Cc: dhowells@...hat.com, linux-fsdevel@...r.kernel.org,
"Matthew Wilcox (Oracle)" <willy@...radead.org>,
Anna Schumaker <anna.schumaker@...app.com>,
Steve French <sfrench@...ba.org>,
Dominique Martinet <asmadeus@...ewreck.org>,
Mike Marshall <hubcap@...ibond.com>,
David Wysochanski <dwysocha@...hat.com>,
Shyam Prasad N <nspmangalore@...il.com>,
Miklos Szeredi <miklos@...redi.hu>,
Linus Torvalds <torvalds@...ux-foundation.org>,
linux-cachefs@...hat.com, linux-afs@...ts.infradead.org,
linux-nfs@...r.kernel.org, linux-cifs@...r.kernel.org,
ceph-devel@...r.kernel.org, v9fs-developer@...ts.sourceforge.net,
devel@...ts.orangefs.org, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 01/12] afs: Sort out symlink reading
Jeff Layton <jlayton@...hat.com> wrote:
> > -static int afs_symlink_readpage(struct page *page)
> > +static int afs_symlink_readpage(struct file *file, struct page *page)
> > {
> > struct afs_vnode *vnode = AFS_FS_I(page->mapping->host);
> > struct afs_read *fsreq;
>
>
> I wonder...would you be better served here by not using page_readlink
> for symlinks and instead use simple_get_link and roll your own readlink
> operation. It seems a bit more direct, and AFS seems to be the only
> caller of page_readlink.
Maybe. At some point it will need to go through netfs_readpage() so that it
will get cached and maybe encrypted. Possibly there should be a
netfs_readlink(). AFS directories too will at some point need to go through
netfs_readahead() or similar.
David
Powered by blists - more mailing lists