All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: Roland Dreier <rdreier@cisco.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] anonfd: Make file read-only if fops->write is not set
Date: Fri, 18 Dec 2009 19:14:04 +0000	[thread overview]
Message-ID: <20091218191404.GJ18217@ZenIV.linux.org.uk> (raw)
In-Reply-To: <alpine.DEB.2.00.0912181057040.24513@makko.or.mcafeemobile.com>

On Fri, Dec 18, 2009 at 10:59:00AM -0800, Davide Libenzi wrote:
> > so would something like this make sense?  if so I'll send follow-ups
> > converting ia64 / perfmon and infiniband / uverbs to anon_inodes.
> 
> Looks OK to me.

fmode_t calculation looks ugly; I'll update and put into VFS tree

      reply	other threads:[~2009-12-18 19:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-18  5:46 [PATCH] anonfd: Make file read-only if fops->write is not set Roland Dreier
2009-12-18  6:10 ` Al Viro
2009-12-18 17:12   ` Davide Libenzi
2009-12-18 17:41   ` [PATCH v2] " Roland Dreier
2009-12-18 18:59     ` Davide Libenzi
2009-12-18 19:14       ` Al Viro [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=20091218191404.GJ18217@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=davidel@xmailserver.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdreier@cisco.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.