All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ed Tomlinson <tomlins@cam.org>
To: Oleg Drokin <green@namesys.com>, Colin Slater <hoho@tacomeat.net>
Cc: reiserfs-list@namesys.com
Subject: Re: Reiserfs broken in 2.5.50 (possibly nanosecond stat timefields?)
Date: Sun, 1 Dec 2002 21:45:48 -0500	[thread overview]
Message-ID: <200212012145.48864.tomlins@cam.org> (raw)
In-Reply-To: <20021130200614.A7766@namesys.com>

On November 30, 2002 12:06 pm, Oleg Drokin wrote:
> Hello!
>
> On Sat, Nov 30, 2002 at 11:48:25AM -0500, Colin Slater wrote:
> > ld.so? My systems is completely reiserfs (3.6), and nothing has
> > changed in my config file between 2.5.47 and 2.5.50. Upon looking
> > through the source tree, it seems like lines 1134-7 in
> > fs/reiserfs/namei.c seem to be throwing this panic. Only changesets to
> > touch namei.c in the past 4 months are "nanosecond stat timefields" and
> > "*_mknod prototype". I really can't see why these would cause this
> > problem, so maybe someone else does. Hand-copied output from the
> > BUG() follows, so this is only what I thought was important and might
> > contain errors. If you need any other information I will gladly supply
> > it.
>
> Just to make sure, does this patch helps?

This also cleared up boot problems I was having with 2.5.50.

Thanks
Ed Tomlinson

  reply	other threads:[~2002-12-02  2:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-30 16:48 Reiserfs broken in 2.5.50 (possibly nanosecond stat timefields?) Colin Slater
2002-11-30 17:06 ` Oleg Drokin
2002-12-02  2:45   ` Ed Tomlinson [this message]
2002-12-02  6:16     ` Oleg Drokin
  -- strict thread matches above, loose matches on Subject: below --
2002-11-30 19:07 Colin Slater
2002-12-02  7:26 ` Oleg Drokin
     [not found] <20021130.104556.59462872.hoho@tacomeat.net.suse.lists.linux.kernel>
2002-11-30 18:43 ` Andi Kleen
2002-11-30 17:59 Colin Slater
2002-11-30 15:45 Colin Slater

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=200212012145.48864.tomlins@cam.org \
    --to=tomlins@cam.org \
    --cc=green@namesys.com \
    --cc=hoho@tacomeat.net \
    --cc=reiserfs-list@namesys.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.