public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Yanchuan Nian <ycnian@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] nfsd: Remove write permission from file content
Date: Tue, 8 Jan 2013 10:18:40 -0500	[thread overview]
Message-ID: <20130108151840.GC16343@fieldses.org> (raw)
In-Reply-To: <CAC5OsZPR88SktqjTKsqJVaxKZ1LkPnvPcT2gPSFq_oPDZ1FZpw@mail.gmail.com>

On Sat, Jan 05, 2013 at 12:29:05PM +0800, Yanchuan Nian wrote:
> 2013/1/5 J. Bruce Fields <bfields@fieldses.org>
> 
> > On Fri, Jan 04, 2013 at 07:45:35PM +0800, ycnian@gmail.com wrote:
> > > From: Yanchuan Nian <ycnian@gmail.com>
> > >
> > > The write function doesn't be implemented in file content, and it's
> > meaningless
> > > to write data into this file directly. Remove write permission from it.
> >
> > So does it really matter either way?
> >
> No, it doesn't matter. I saw that nfs-utils communicates with nfsd through
> proc fs, so I tried to update the cache by writing data to proc fs
> directly. I found the format of "channel" and "flush" in nfs-utils, but I
> couldn't find the format of "content", so I read the sunrpc source code,
> and found that the write function doesn't be implemented, but the write
> permission is set when registering into proc fs. I also found that
> "content" in pipe fs doesn't have write permission.

OK, so if it had been read-only it might have saved you a little
confusion.  Fair enough.

--b.

> 
> >
> > OK, applying, but I wonder.
> >
> > --b.
> >
> > >
> > > Signed-off-by: Yanchuan Nian <ycnian@gmail.com>
> > > ---
> > >  net/sunrpc/cache.c |    2 +-
> > >  1 files changed, 1 insertions(+), 1 deletions(-)
> > >
> > > diff --git a/net/sunrpc/cache.c b/net/sunrpc/cache.c
> > > index 9afa439..9f84703 100644
> > > --- a/net/sunrpc/cache.c
> > > +++ b/net/sunrpc/cache.c
> > > @@ -1614,7 +1614,7 @@ static int create_cache_proc_entries(struct
> > cache_detail *cd, struct net *net)
> > >                       goto out_nomem;
> > >       }
> > >       if (cd->cache_show) {
> > > -             p = proc_create_data("content", S_IFREG|S_IRUSR|S_IWUSR,
> > > +             p = proc_create_data("content", S_IFREG|S_IRUSR,
> > >                               cd->u.procfs.proc_ent,
> > >                               &content_file_operations_procfs, cd);
> > >               cd->u.procfs.content_ent = p;
> > > --
> > > 1.7.4.4
> > >
> >

      parent reply	other threads:[~2013-01-08 15:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-04 11:45 [PATCH] nfsd: Remove write permission from file content ycnian
2013-01-04 21:12 ` J. Bruce Fields
     [not found]   ` <CAC5OsZPR88SktqjTKsqJVaxKZ1LkPnvPcT2gPSFq_oPDZ1FZpw@mail.gmail.com>
2013-01-08 15:18     ` J. Bruce Fields [this message]

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=20130108151840.GC16343@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=ycnian@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