linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Kleikamp <shaggy@linux.vnet.ibm.com>
To: Harry Papaxenopoulos <harry@cs.sunysb.edu>
Cc: linux-ext4@vger.kernel.org, ezk@cs.sunysb.edu, kolya@cs.sunysb.edu
Subject: Re: [Resubmit][PATCH 5/5] Secure Deletion and Trash-Bin Support for Ext4
Date: Thu, 01 Feb 2007 07:19:58 -0600	[thread overview]
Message-ID: <1170335998.12263.4.camel@kleikamp.austin.ibm.com> (raw)
In-Reply-To: <Pine.GSO.4.53.0701311951100.4753@compserv1>

On Thu, 2007-02-01 at 06:05 -0500, Harry Papaxenopoulos wrote:
> 
> On Wed, 31 Jan 2007, Dave Kleikamp wrote:

> > why not unconditionally goto out here?  if vfs_trash_entry() was
> > successful, the file was successfully moved to the trashbin directory.
> > There is nothing left to be done, right?  Then there's no need for the
> > trashed flag.
> >
> > In fact, the ifdef'ed code should precede the call to get_UCSname(),
> > since we don't need to allocate dname if we move the file to the
> > trashbin, and we leak the allocation if we jump to out:.
> >
> 
> Well the main reason I don't jump to out is to update the inode's
> change time, otherwise I would have unconditionally jumped.

the rename already updates the change time.
> 
> You're right, I used the incorrect label to jump. Should have been "out1"
> instead of "out" so the allocation is freed. Sorry about that.

I'd rather do the allocation after the new code anyway.  It's not needed
at all if we're moving the file to the trashbin.

Thanks,
Shaggy
-- 
David Kleikamp
IBM Linux Technology Center

  reply	other threads:[~2007-02-01 13:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-31 14:55 [Resubmit][PATCH 5/5] Secure Deletion and Trash-Bin Support for Ext4 Harry Papaxenopoulos
2007-01-31 17:11 ` Dave Kleikamp
2007-02-01 11:05   ` Harry Papaxenopoulos
2007-02-01 13:19     ` Dave Kleikamp [this message]
2007-02-01 17:17   ` Nikolai Joukov
2007-02-01 19:32     ` Dave Kleikamp
2007-02-01 20:41       ` Mingming Cao
2007-02-02  1:40         ` Andreas Dilger
2007-02-02  2:22           ` Dave Kleikamp
2007-02-06  3:48             ` Theodore Tso
2007-02-25 10:33   ` Andrew Morton

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=1170335998.12263.4.camel@kleikamp.austin.ibm.com \
    --to=shaggy@linux.vnet.ibm.com \
    --cc=ezk@cs.sunysb.edu \
    --cc=harry@cs.sunysb.edu \
    --cc=kolya@cs.sunysb.edu \
    --cc=linux-ext4@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).