From: Olivier Galibert <galibert@pobox.com>
To: Chuck Ebbert <cebbert@redhat.com>
Cc: Ian Kent <raven@themaw.net>,
"Hack inc." <linux-kernel@vger.kernel.org>,
autofs@linux.kernel.org
Subject: Re: [PATCH 1/2] Re: [autofs] Bad race condition in the new autofs protocol somewhere
Date: Tue, 13 Feb 2007 16:54:05 +0100 [thread overview]
Message-ID: <20070213155405.GA33765@dspnet.fr.eu.org> (raw)
In-Reply-To: <45D1C61F.9090509@redhat.com>
On Tue, Feb 13, 2007 at 09:07:27AM -0500, Chuck Ebbert wrote:
> Olivier Galibert wrote:
> > On Tue, Feb 13, 2007 at 09:52:39AM +0900, Ian Kent wrote:
> >> Indeed.
> >> Which kernel can you use?
> >> I believe that 2200 had another problem so can you use an fc5 kernel
> >> later than that?
> >
> > I've ported your patch to 2257 (nothing special, only moved lines),
> > and it seems to work beautifully. I'm enlarging the testing.
> >
>
> If you get the patches into -stable they will end up in Fedora
> kernels automatically. 2288 (based on 2.6.19) is in testing now...
Don't they require autofs5 to be of any use though? That's not going
to be in fc until it's out of beta I guess.
OG.
next prev parent reply other threads:[~2007-02-13 15:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-07 17:34 Bad race condition in the new autofs protocol somewhere Olivier Galibert
2007-02-07 18:07 ` [autofs] " Ian Kent
2007-02-07 18:18 ` Olivier Galibert
2007-02-08 2:33 ` Ian Kent
2007-02-12 6:43 ` [PATCH 1/2] " Ian Kent
2007-02-12 6:46 ` [PATCH 2/2] " Ian Kent
2007-02-12 13:57 ` [PATCH 1/2] " Olivier Galibert
2007-02-13 0:52 ` Ian Kent
2007-02-13 8:50 ` Olivier Galibert
2007-02-13 13:40 ` Ian Kent
2007-02-13 14:07 ` Chuck Ebbert
2007-02-13 15:54 ` Olivier Galibert [this message]
2007-02-13 15:57 ` Chuck Ebbert
2007-02-13 17:35 ` Ian Kent
2007-02-13 20:43 ` Olivier Galibert
2007-02-13 17:29 ` Ian Kent
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=20070213155405.GA33765@dspnet.fr.eu.org \
--to=galibert@pobox.com \
--cc=autofs@linux.kernel.org \
--cc=cebbert@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=raven@themaw.net \
/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.