All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Halbert <halbert@everyzing.com>
To: autofs@kernel.org
Subject: Re: ENOENT on first reference to an automounted file
Date: Fri, 19 Oct 2007 09:20:21 -0400	[thread overview]
Message-ID: <4718AF15.3090204@everyzing.com> (raw)
In-Reply-To: <1192780957.24353.10.camel@raven.themaw.net>

Ian Kent wrote:
> 
> Well, if we can't confirm the problem and resolution then I have no case
> to put for an update.
> 
> No-one has volunteered to try the patches I referred to in this thread
> and that's why I haven't posted them, so how about it, someone?

Ian (& Greg & Jeff),

Maybe there's a bit of cross-purpose communication here. In an earlier 
message, Jeff said he had reproduced the problem by using exactly our 
kernel (2.6.9-55.0.9.ELsmp x86_64), and that the problem did NOT happen 
with a later kernel he had (which was the one he originally tried). See 
http://linux.kernel.org/pipermail/autofs/2007-October/004133.html.

So I think Jeff has confirmed the problem and resolution. Am I telling 
you something you already know?

Jeff said his successful test kernel has patches for bug 248126. Comment 
#24 in that bug says the patch was put in 2.6.9-55.0.7. So I'd expect 
the patch to be in 2.6.9-55.0.9 and for the problem to be fixed already. 
Since it isn't fixed, either the patch was pulled between .7 and .9, or 
the fix is more complicated than that single patch. Also, the bug 
comments refer to several different patch sets and other bugs, so it's 
not clear to me which patches Jeff actually has in his test kernel.

My group has various workarounds, so we're not dead in the water. We are 
also might move up to 5.x, but are waiting for a completely different 
fix as well (kernel.org bug #7768), which is not yet in the released 
upstream kernels.

Dan

  reply	other threads:[~2007-10-19 13:20 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-18 10:36 ENOENT on first reference to an automounted file Greg Earle
2007-10-19  8:02 ` Ian Kent
2007-10-19 13:20   ` Dan Halbert [this message]
2007-10-19 14:37     ` Ian Kent
2007-10-19 15:22       ` Jeff Moyer
2007-10-19 17:05         ` Dan Halbert
2007-10-19 17:21           ` Ian Kent
2007-11-03 15:27             ` Dan Halbert
2007-11-04  5:12               ` Ian Kent
     [not found] <mailman.446.1194400455.3098.autofs@linux.kernel.org>
2007-11-17 21:25 ` Greg Earle
2007-11-18  2:46   ` Ian Kent
     [not found] <mailman.1.1192795201.25176.autofs@linux.kernel.org>
2007-10-20  1:28 ` ENOENT on first reference to an automounted file To: autofs@linux.kernel.org Greg Earle
2007-11-07  1:53   ` ENOENT on first reference to an automounted file Dan Halbert
  -- strict thread matches above, loose matches on Subject: below --
2007-10-05 21:14 Dan Halbert
2007-10-06  4:48 ` Ian Kent
2007-10-08 15:15   ` Jeff Moyer
     [not found]   ` <47081453.7000709@everyzing.com>
2007-10-08 16:29     ` Jeff Moyer
2007-10-08 16:35       ` Dan Halbert
2007-10-08 16:43         ` Jeff Moyer
2007-10-08 17:20         ` Jeff Moyer
2007-10-08 18:00           ` Dan Halbert
2007-10-09  3:11             ` 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=4718AF15.3090204@everyzing.com \
    --to=halbert@everyzing.com \
    --cc=autofs@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 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.