From: Willy Tarreau <willy@w.ods.org>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: Dimitris Zilaskos <dzila@tassadar.physics.auth.gr>,
openafs-info@openafs.org, linux-kernel@vger.kernel.org
Subject: Re: Openafs 1.3.78 and kernel 2.4.29 oopses , same for 2.4.30 and openafs 1.3.82
Date: Sat, 7 May 2005 12:06:51 +0200 [thread overview]
Message-ID: <20050507100651.GA18380@alpha.home.local> (raw)
In-Reply-To: <20050506165033.GA2105@logos.cnet>
On Fri, May 06, 2005 at 01:50:33PM -0300, Marcelo Tosatti wrote:
> > > Oopses on an openafs client system using openafs 1.3.78 and kernel 2.4.29.
> > > Oopses also occur afer moving to kernel 2.4.30 and openafs 1.3.82
> >
> > The problem you encounter on 2.4.30 is not the same as on 2.4.29. The problem
> > in 2.4.29 is related to link_path_walk, which has been fixed in 2.4.30.
>
> Willy,
>
> The link_path_walk fix in v2.4.30 is related to a reference counting
> bug triggered by "umount"...
Hmmm... you're right Marcelo, sorry for the confusion. When I saw
'link_path_walk' in Dimitris' trace, it recalled me something, and I saw
the recent fix for an oops which I thought related, but apparently not.
> As Christoph noted OpenAFS seems to be doing nasty things... it seems
> to play with dentries inode i_state directly? If that is the case,
> maybe it should define d_iput?
I don't know, but clearly if it's doing dirty tricks, it's not surprizing
that even small changes from 2.4.29 to 2.4.30 can trigger or hide the bugs.
He should try to decorellate openafs and kernel versions. Trying 1.3.82 on
top of 2.4.29 (or even -hf) would probably show that he gets the same bugs
as on 2.4.30, thus leading to the conclusion that the difference lies in
the openafs upgrade.
Cheers,
Willy
prev parent reply other threads:[~2005-05-07 10:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-05 23:55 Dimitris Zilaskos
2005-05-06 5:28 ` Willy Tarreau
2005-05-06 7:28 ` Dimitris Zilaskos
2005-05-06 14:23 ` chas williams - CONTRACTOR
2005-05-06 14:42 ` Christoph Hellwig
2005-05-06 14:44 ` Dimitris Zilaskos
2005-05-06 16:50 ` Marcelo Tosatti
2005-05-07 9:51 ` Dimitris Zilaskos
2005-05-07 10:09 ` Willy Tarreau
2005-05-07 11:51 ` Dimitris Zilaskos
2005-05-07 12:08 ` Willy Tarreau
2005-05-09 10:03 ` Dimitris Zilaskos
2005-05-07 10:06 ` Willy Tarreau [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=20050507100651.GA18380@alpha.home.local \
--to=willy@w.ods.org \
--cc=dzila@tassadar.physics.auth.gr \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=openafs-info@openafs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®