All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ondrej Valousek <webserv@s3group.cz>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: "autofs@linux.kernel.org" <autofs@linux.kernel.org>
Subject: Re: automounter segfaults when using negative cache?
Date: Mon, 08 Dec 2008 10:08:35 +0100	[thread overview]
Message-ID: <493CE413.5050905@s3group.cz> (raw)
In-Reply-To: <x497i6e6291.fsf@segfault.boston.devel.redhat.com>


>> I thought all the negative caching is done in user space, but apparently
>> kernel has some influence here....
>> Any explanation?
>>     
>
> The negative caching is done in userspace.  I'm not sure I understand
> your question.
>
> Cheers,
> Jeff
>   


Hi Jeff,
Ok I was thinking this way:
I experience this only on U7 system running U4 kernel - on the same U7
system running U7 kernel I can not replicate this. If the negative
caching is done in the user space and there is a bug there which causes
the autofs to segfault, how is it possible that is won't segfault on the
U7 kernel?
I do not know I am still trying to find out if there is any connection
to the problem with the automounter hanging that I reported earlier as:
- in U7 system running U7 kernel, the autofs does not crash, but hangs
(after few days).
- in U7 system running U4 kernel, the autofs forks crash regularly but
otherwise it works fine (I mean at least the parent autofs fork continue
living...)
You know what I am trying to say?
Thanks,
Ondrej

      parent reply	other threads:[~2008-12-08  9:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-04 11:15 automounter segfaults when using negative cache? Ondrej Valousek
2008-12-05 16:00 ` Jeff Moyer
2008-12-05 16:23   ` Ian Kent
2008-12-05 16:27     ` Jeff Moyer
2008-12-05 17:12       ` Ian Kent
2008-12-08  9:08   ` Ondrej Valousek [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=493CE413.5050905@s3group.cz \
    --to=webserv@s3group.cz \
    --cc=autofs@linux.kernel.org \
    --cc=jmoyer@redhat.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 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.