From: "Mike Snitzer" <snitzer@gmail.com>
To: "Theodore Tso" <tytso@mit.edu>
Cc: "Thomas Trauner" <tt@it-austria.net>,
linux-ext4@vger.kernel.org, ext3-users <ext3-users@redhat.com>,
eugene@ibrix.com
Subject: Re: duplicate entries on ext3 when using readdir/readdir64
Date: Thu, 14 Aug 2008 19:27:45 -0400 [thread overview]
Message-ID: <170fa0d20808141627i7f05fbcdnf043e090834940dd@mail.gmail.com> (raw)
In-Reply-To: <20080814025821.GA6469@mit.edu>
On Wed, Aug 13, 2008 at 10:58 PM, Theodore Tso <tytso@mit.edu> wrote:
> On Wed, Aug 13, 2008 at 05:21:20PM -0400, Mike Snitzer wrote:
>>
>> The attached patch has served my employer (IBRIX) well for 2.5 years.
>> It was only recently, when I re-raised this issue internally based on
>> this thread, that a co-worker recalled the fix.
>>
>
> The patch looks good. Did someone raise it 2.5 years ago, and we
> somehow dropped the ball, or did no one think to submit the patch
> upstream?
We intended to push this fix upstream but doing so got inadvertently
overlooked as we put focus to new issues. I mentioned how long ago
this patch was developed purely to help illustrate the stability of
the fix.
> Also, can I get a Signed-off-by: line for this patch?
Eugene Dashevsky authored the patch; I refreshed it against 2.6.27-rc3:
Signed-off-by: Eugene Dashevsky <eugene@ibrix.com>
Signed-off-by: Mike Snitzer <msnitzer@ibrix.com>
thanks,
Mike
next prev parent reply other threads:[~2008-08-14 23:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1217583820.12454.20.camel@kannnix.a2x.lan.at>
[not found] ` <20080801121658.GG8736@mit.edu>
[not found] ` <1217933631.14552.45.camel@kannnix.a2x.lan.at>
2008-08-06 14:07 ` duplicate entries on ext3 when using readdir/readdir64 Theodore Tso
2008-08-06 15:14 ` Thomas Trauner
2008-08-13 21:21 ` Mike Snitzer
2008-08-14 2:58 ` Theodore Tso
2008-08-14 23:27 ` Mike Snitzer [this message]
2008-08-14 14:52 ` Theodore Tso
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=170fa0d20808141627i7f05fbcdnf043e090834940dd@mail.gmail.com \
--to=snitzer@gmail.com \
--cc=eugene@ibrix.com \
--cc=ext3-users@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tt@it-austria.net \
--cc=tytso@mit.edu \
/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