linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Kleikamp <shaggy@austin.ibm.com>
To: Michael Thompson <michael.craig.thompson@gmail.com>
Cc: Phillip Hellewell <phillip@hellewell.homeip.net>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	mike@halcrow.us, mhalcrow@us.ibm.com, mcthomps@us.ibm.com,
	yoder1@us.ibm.com
Subject: Re: [PATCH 12/12: eCryptfs] Crypto functions
Date: Thu, 03 Nov 2005 16:30:09 -0600	[thread overview]
Message-ID: <1131057009.9365.21.camel@kleikamp.austin.ibm.com> (raw)
In-Reply-To: <afcef88a0511031425u1fa5838fic86cbd7a341cb0a6@mail.gmail.com>

On Thu, 2005-11-03 at 16:25 -0600, Michael Thompson wrote:
> On 11/3/05, Dave Kleikamp <shaggy@austin.ibm.com> wrote:
> > On Wed, 2005-11-02 at 20:56 -0700, Phillip Hellewell wrote:
> > > +       ecryptfs_fput(lower_file);
> >
> > Why the call to ecryptfs_fput() here?  The caller does it's own fput on
> > lower_file.
> 
> Hmm, good catch. That slipped through us - and to be hoenst, I have no
> explination other than, it's wrong. ecryptfs_write_headers should not
> be responsible for put'ing that which it did not get.
> 
> I'm wondering if I should be sending 1 patch per tiny fix like this,
> or if I should be waiting for a few more changes, so as to not flood
> the threads with minor patches?

Well, I found it trying to look for the cause of bug 1228303, but I
haven't actually run anything to verify it.  It may be worth checking if
it fixes that problem, and if it does, it would bump up its importance.

> Thanks,
> Mike
> 
-- 
David Kleikamp
IBM Linux Technology Center

  reply	other threads:[~2005-11-03 22:30 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-03  3:32 [PATCH 0/12: eCryptfs] eCryptfs version 0.1 Phillip Hellewell
2005-11-03  3:42 ` [PATCH 1/12: eCryptfs] Makefile and Kconfig Phillip Hellewell
2005-11-03 15:21   ` Michael Thompson
2005-11-03 23:05     ` Greg KH
2005-11-04 16:09       ` Michael Thompson
2005-11-04 16:22         ` Anton Altaparmakov
2005-11-04 16:28           ` Michael Thompson
2005-11-04 16:35         ` Greg KH
2005-11-04 17:07           ` Michael Thompson
2005-11-03  3:43 ` [PATCH 2/12: eCryptfs] Documentation Phillip Hellewell
2005-11-03  3:43 ` [PATCH 3/12: eCryptfs] Makefile Phillip Hellewell
2005-11-03  3:49 ` [PATCH 4/12: eCryptfs] Main module functions Phillip Hellewell
2005-11-03  6:02   ` Greg KH
2005-11-03 15:09     ` Michael Thompson
2005-11-03 15:47       ` Alexey Dobriyan
2005-11-03 15:40         ` Michael Thompson
2005-11-03 21:34     ` Michael Thompson
2005-11-04 23:28     ` [PATCH: eCryptfs] Remove debug wrappers Michael Halcrow
2005-11-03  3:50 ` [PATCH 5/12: eCryptfs] Header declarations Phillip Hellewell
2005-11-03 23:37   ` James Morris
2005-11-03  3:51 ` [PATCH 6/12: eCryptfs] Superblock operations Phillip Hellewell
2005-11-03 23:47   ` James Morris
2005-11-03  3:52 ` [PATCH 7/12: eCryptfs] File operations Phillip Hellewell
2005-11-03 23:49   ` James Morris
2005-11-03  3:53 ` [PATCH 8/12: eCryptfs] Dentry operations Phillip Hellewell
2005-11-03  3:54 ` [PATCH 9/12: eCryptfs] Inode operations Phillip Hellewell
2005-11-03 23:51   ` James Morris
2005-11-04  0:24     ` Andreas Schwab
2005-11-04  6:29       ` James Morris
2005-11-03  3:55 ` [PATCH 10/12: eCryptfs] Mmap operations Phillip Hellewell
2005-11-03  5:32   ` Michael Halcrow
2005-11-07 20:39     ` [PATCH: eCryptfs] Encrypt on writepage() Michael Halcrow
2005-11-03  3:56 ` [PATCH 11/12: eCryptfs] Keystore Phillip Hellewell
2005-11-03 23:59   ` James Morris
2005-11-04  0:08     ` Michael Halcrow
2005-11-04 17:52   ` Timothy R. Chavez
2005-11-03  3:56 ` [PATCH 12/12: eCryptfs] Crypto functions Phillip Hellewell
2005-11-03 22:06   ` Dave Kleikamp
2005-11-03 22:25     ` Michael Thompson
2005-11-03 22:30       ` Dave Kleikamp [this message]
2005-11-04  0:08   ` James Morris
2005-11-04  0:14     ` Michael Halcrow
  -- strict thread matches above, loose matches on Subject: below --
2005-11-19  4:11 [PATCH 0/12: eCryptfs] eCryptfs version 0.1 Phillip Hellewell
2005-11-19  4:23 ` [PATCH 12/12: eCryptfs] Crypto functions Phillip Hellewell

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=1131057009.9365.21.camel@kleikamp.austin.ibm.com \
    --to=shaggy@austin.ibm.com \
    --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=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 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).