From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Willy Tarreau <willy@w.ods.org>
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: Fri, 6 May 2005 13:50:33 -0300 [thread overview]
Message-ID: <20050506165033.GA2105@logos.cnet> (raw)
In-Reply-To: <20050506052803.GE777@alpha.home.local>
On Fri, May 06, 2005 at 07:28:03AM +0200, Willy Tarreau wrote:
> Hi,
>
> On Fri, May 06, 2005 at 02:55:40AM +0300, Dimitris Zilaskos wrote:
> >
> > Hello ,
> >
> > [1.] One line summary of the problem:
> >
> > 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.
>
> You might want to try 1.3.78 (or other) with 2.4.29-hf7 to check if your
> 2.4.30 problem was brought by kernel 2.4.30 or openafs 1.3.82, as the
> link_path_walk bug is also fixed in hf7. The patch is available on :
Willy,
The link_path_walk fix in v2.4.30 is related to a reference counting
bug triggered by "umount"...
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?
static inline void dentry_iput(struct dentry * dentry)
{
struct inode *inode = dentry->d_inode;
if (inode) {
dentry->d_inode = NULL;
list_del_init(&dentry->d_alias);
spin_unlock(&dcache_lock);
if (dentry->d_op && dentry->d_op->d_iput)
dentry->d_op->d_iput(dentry, inode);
May 6 04:55:29 system kernel: kernel BUG at inode.c:1204!
next prev parent reply other threads:[~2005-05-06 21:25 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 [this message]
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
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=20050506165033.GA2105@logos.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=dzila@tassadar.physics.auth.gr \
--cc=linux-kernel@vger.kernel.org \
--cc=openafs-info@openafs.org \
--cc=willy@w.ods.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
Powered by JetHome