All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Michael Thompson <michael.craig.thompson@gmail.com>
Cc: Phillip Hellewell <phillip@hellewell.homeip.net>,
	akpm@osdl.org, linux-kernel@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, viro@ftp.linux.org.uk,
	mike@halcrow.us, mhalcrow@us.ibm.com, mcthomps@us.ibm.com,
	yoder1@us.ibm.com
Subject: Re: [PATCH 6/12: eCryptfs] Superblock operations
Date: Mon, 21 Nov 2005 18:01:56 +0200	[thread overview]
Message-ID: <1132588916.8487.3.camel@localhost> (raw)
In-Reply-To: <afcef88a0511210757y4fdb8c57w221b0fc9e7ee3ee4@mail.gmail.com>

Hi,

On 11/19/05, Pekka Enberg <penberg@cs.helsinki.fi> wrote:
> > > +/**
> > > + * This is called through iput_final().
> > > + * This is function will replace generic_drop_inode. The end result of which
> > > + * is we are skipping the check in inode->i_nlink, which we do not use.
> > > + */
> > > +static void ecryptfs_drop_inode(struct inode *inode) {
> > > +       generic_delete_inode(inode);
> > > +}
> >
> > Please drop this useless wrapper and introduce it when it actually
> > does something.

On Mon, 2005-11-21 at 09:57 -0600, Michael Thompson wrote:
> I don't see a problem with doing that, but perhaps there is? Please
> elaborate if so.

You can set ecryptfs_sops->drop_inode to generic_delete_inode directly,
no?

			Pekka


  reply	other threads:[~2005-11-21 16:02 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-19  4:11 [PATCH 0/12: eCryptfs] eCryptfs version 0.1 Phillip Hellewell
2005-11-19  4:14 ` [PATCH 1/12: eCryptfs] Makefile and Kconfig Phillip Hellewell
2005-11-19  4:16 ` [PATCH 2/12: eCryptfs] Documentation Phillip Hellewell
2005-11-19  4:16 ` [PATCH 3/12: eCryptfs] Makefile Phillip Hellewell
2005-11-19  4:17 ` [PATCH 4/12: eCryptfs] Main module functions Phillip Hellewell
2005-11-19 10:47   ` Pekka Enberg
2005-11-20 15:34     ` Anton Altaparmakov
2005-11-20 19:06       ` Pekka Enberg
2005-11-21 16:10     ` Michael Thompson
2005-11-21 16:12       ` Michael Thompson
2005-11-21 16:21       ` Pekka Enberg
2005-11-19  4:18 ` [PATCH 5/12: eCryptfs] Header declarations Phillip Hellewell
2005-11-19 10:37   ` Pekka Enberg
2005-11-21 15:50     ` Michael Thompson
2005-11-19  4:19 ` [PATCH 6/12: eCryptfs] Superblock operations Phillip Hellewell
2005-11-19 10:50   ` Pekka Enberg
2005-11-21 15:57     ` Michael Thompson
2005-11-21 16:01       ` Pekka Enberg [this message]
2005-11-21 16:13         ` Michael Thompson
2005-11-21 16:15           ` Michael Thompson
2005-11-21 16:20             ` Pekka Enberg
2005-11-19  4:20 ` [PATCH 7/12: eCryptfs] File operations Phillip Hellewell
2005-11-19 10:53   ` Pekka Enberg
2005-11-21 15:58     ` Michael Thompson
2005-11-19  4:20 ` [PATCH 8/12: eCryptfs] Dentry operations Phillip Hellewell
2005-11-19  4:21 ` [PATCH 9/12: eCryptfs] Inode operations Phillip Hellewell
2005-11-19  4:22 ` [PATCH 10/12: eCryptfs] Mmap operations Phillip Hellewell
2005-11-19  4:23 ` [PATCH 11/12: eCryptfs] Keystore Phillip Hellewell
2005-11-19  4:23 ` [PATCH 12/12: eCryptfs] Crypto functions Phillip Hellewell
2005-11-19  6:16 ` [PATCH 0/12: eCryptfs] eCryptfs version 0.1 Andrew Morton
2005-11-21 20:28   ` Michael Halcrow
2005-11-21 21:41     ` James Morris
2005-11-21 22:11       ` Michael Thompson
  -- strict thread matches above, loose matches on Subject: below --
2005-11-03  3:32 Phillip Hellewell
2005-11-03  3:51 ` [PATCH 6/12: eCryptfs] Superblock operations Phillip Hellewell
2005-11-03 23:47   ` James Morris

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=1132588916.8487.3.camel@localhost \
    --to=penberg@cs.helsinki.fi \
    --cc=akpm@osdl.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcthomps@us.ibm.com \
    --cc=mhalcrow@us.ibm.com \
    --cc=michael.craig.thompson@gmail.com \
    --cc=mike@halcrow.us \
    --cc=phillip@hellewell.homeip.net \
    --cc=viro@ftp.linux.org.uk \
    --cc=yoder1@us.ibm.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.