linux-kernel - Re: [ltt-dev] [PATCH] nfs: add support for splice writes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1240237274.13636.9.camel@heimdal.trondhjem.org>
Date:	Mon, 20 Apr 2009 10:21:14 -0400
From:	Trond Myklebust <trond.myklebust@....uio.no>
To:	Suresh Jayaraman <sjayaraman@...e.de>
Cc:	Masahiro Tamori <masahiro.tamori@...il.com>,
	Mathieu Desnoyers <compudj@...stal.dyndns.org>,
	linux-nfs@...r.kernel.org, ltt-dev@...ts.casi.polymtl.ca,
	LKML <linux-kernel@...r.kernel.org>,
	linux-embedded@...r.kernel.org,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: [ltt-dev] [PATCH] nfs: add support for splice writes

On Mon, 2009-04-20 at 18:08 +0530, Suresh Jayaraman wrote:
> Trond Myklebust wrote:
> > On Mon, 2009-04-20 at 11:09 +0530, Suresh Jayaraman wrote:
> >> Hi Trond,
> >>
> >> Do you think this patch is OK? Can this be considered for merging?
> >>
> >> Thanks,
> >>
> >>>>>> diff --git a/fs/nfs/file.c b/fs/nfs/file.c
> >>>>>> index 90f292b..13d6a00 100644
> >>>>>> --- a/fs/nfs/file.c
> >>>>>> +++ b/fs/nfs/file.c
> >>>>>> @@ -47,6 +47,9 @@ static ssize_t nfs_file_splice_read(struct file *filp, loff_t *ppos,
> >>>>>>                   size_t count, unsigned int flags);
> >>>>>> static ssize_t nfs_file_read(struct kiocb *, const struct iovec *iov,
> >>>>>>               unsigned long nr_segs, loff_t pos);
> >>>>>> +static ssize_t nfs_file_splice_write(struct pipe_inode_info *pipe,
> >>>>>> +                  struct file *filp, loff_t *ppos,
> >>>>>> +                  size_t count, unsigned int flags);
> >>>>>> static ssize_t nfs_file_write(struct kiocb *, const struct iovec *iov,
> >>>>>>               unsigned long nr_segs, loff_t pos);
> >>>>>> static int nfs_file_flush(struct file *, fl_owner_t id);
> >>>>>> @@ -76,6 +79,7 @@ const struct file_operations nfs_file_operations = {
> >>>>>>   .lock      = nfs_lock,
> >>>>>>   .flock     = nfs_flock,
> >>>>>>   .splice_read  = nfs_file_splice_read,
> >>>>>> +  .splice_write  = nfs_file_splice_write,
> >>>>>>   .check_flags  = nfs_check_flags,
> >>>>>>   .setlease    = nfs_setlease,
> >>>>>> };
> >>>>>> @@ -550,6 +554,26 @@ out_swapfile:
> >>>>>>   goto out;
> >>>>>> }
> >>>>>>
> >>>>>> +static ssize_t nfs_file_splice_write(struct pipe_inode_info *pipe,
> >>>>>> +                 struct file *filp, loff_t *ppos,
> >>>>>> +                 size_t count, unsigned int flags)
> >>>>>> +{
> >>>>>> +  struct dentry *dentry = filp->f_path.dentry;
> >>>>>> +  struct inode *inode = dentry->d_inode;
> >>>>>> +
> >>>>>> +  dprintk("NFS splice_write(%s/%s, %lu@%Lu)\n",
> >>>>>> +      dentry->d_parent->d_name.name, dentry->d_name.name,
> >>>>>> +      (unsigned long) count, (unsigned long long) *ppos);
> >>>>>> +
> >>>>>> +  if (IS_SWAPFILE(inode)) {
> >>>>>> +      printk(KERN_INFO "NFS: attempt to write to active swap"
> >>>>>> +          "file!\n");
> >>>>>> +      return -EBUSY;
> >>>>>> +  }
> > 
> > I don't know that we really need this. We should sweep through the NFS
> > code and kill all those IS_SWAPFILE() thingys. Or at least #define
> > IS_SWAPFILE(a) (0)
> > ...
> 
> Hmm.. I'm not sure whether we should kill them now. I think originally,
> these were added keeping in mind the future NFS swap support. Given that
> the recent work from Peterz Zilstra on "Swap over NFS" and multiple
> iterations/review on the same, I think those patches will eventually get
> merged sooner or later. Perhaps, it's a good idea to #define
> IS_SWAPFILE(a) 0 than killing them entirely..?

Why are they needed at all? AFAICS, other filesystems check IS_SWAPFILE
when truncating a file, but don't litter their code with all these weird
checks for writing, reading, etc.
It's not as if these checks can stop a determined privileged person from
writing to the swapfile anyway. All they have to do is go to another
client or write directly to the file on the server...

Trond

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/