From: Christoph Hellwig <hch@infradead.org>
To: chas3@users.sourceforge.net
Cc: Dimitris Zilaskos <dzila@tassadar.physics.auth.gr>,
Willy Tarreau <willy@w.ods.org>,
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 15:42:07 +0100 [thread overview]
Message-ID: <20050506144207.GA2604@infradead.org> (raw)
In-Reply-To: <200505061423.j46ENfTG024192@ginger.cmf.nrl.navy.mil>
On Fri, May 06, 2005 at 10:23:42AM -0400, chas williams - CONTRACTOR wrote:
> In message <Pine.LNX.4.62.0505061024070.450@tassadar.physics.auth.gr>,Dimitris
> Zilaskos writes:
> >May 6 04:55:29 system kernel: kernel BUG at inode.c:1204!
>
> looks like you might have one of those kernels with extra bits (in
> particular, i_notify). please try a later version of afs like 1.3.81.
Btw, we get tons of bugsreports like that lately. Is there a chance
that the OpenAFS folks could get their act together and stop abusing
internal interfaces all over. In particular please stop shadowing struct
inode with your own version and use the proper export operations interfaces
if you're searching for an inode on another filesystem instead of the
utterly wrong blind iget().
next prev parent reply other threads:[~2005-05-06 14:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-05 23:55 Openafs 1.3.78 and kernel 2.4.29 oopses , same for 2.4.30 and openafs 1.3.82 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 [this message]
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
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=20050506144207.GA2604@infradead.org \
--to=hch@infradead.org \
--cc=chas3@users.sourceforge.net \
--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 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.