From: Dmitriy Monakhov <dmonakhov@sw.ru>
To: Michael Halcrow <lkml@halcrow.us>
Cc: Dmitriy Monakhov <dmonakhov@sw.ru>,
linux-kernel@vger.kernel.org,
ecryptfs-devel@lists.sourceforge.net, devel@openvz.org
Subject: Re: [Ecryptfs-devel] [PATCH] ecryptfs lower_file largefile issue
Date: Wed, 21 Feb 2007 16:45:17 +0300 [thread overview]
Message-ID: <87abz7r5ea.fsf@sw.ru> (raw)
In-Reply-To: <20070221130614.GN10765@halcrow.us> (Michael Halcrow's message of "Wed, 21 Feb 2007 07:06:14 -0600")
Michael Halcrow <lkml@halcrow.us> writes:
> On Wed, Feb 21, 2007 at 01:07:22PM +0300, Dmitriy Monakhov wrote:
>> Where is largefile issue in ecryptfs.
>
> Thanks for your thorough work on resolving such issues. We will
> integrate your patches and testcases into the next release as soon as
> we get a chance to review and test.
BTW previously i've sent some patches for ecryptfs to lkml but forgot add
ecryptfs-devel@lists.sourceforge.net to CC:.
links to patches:
"ecryptfs lower_file handling issues" http://lkml.org/lkml/2007/2/19/147
"ecryptfs_read_super path_lookup" errh fix http://lkml.org/lkml/2007/2/19/171
>
> Mike
> .___________________________________________________________________.
> Michael A. Halcrow
> Security Software Engineer, IBM Linux Technology Center
> GnuPG Fingerprint: 419C 5B1E 948A FA73 A54C 20F5 DB40 8531 6DCA 8769
>
> "To prohibit sharing software is to cut the bonds of society."
> - Richard Stallman
prev parent reply other threads:[~2007-02-21 13:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-21 10:07 [PATCH] ecryptfs lower_file largefile issue Dmitriy Monakhov
2007-02-21 13:06 ` [Ecryptfs-devel] " Michael Halcrow
2007-02-21 13:45 ` Dmitriy Monakhov [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=87abz7r5ea.fsf@sw.ru \
--to=dmonakhov@sw.ru \
--cc=devel@openvz.org \
--cc=ecryptfs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@halcrow.us \
/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