public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Oleg Drokin <green@namesys.com>
To: Stephan von Krawczynski <skraw@ithnet.com>
Cc: marcelo@conectiva.com.br, akpm@osdl.org, andrea@suse.de,
	alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org,
	mason@suse.com
Subject: Re: 2.4.22-pre lockups (now decoded oops for pre10)
Date: Fri, 15 Aug 2003 14:31:04 +0400	[thread overview]
Message-ID: <20030815103104.GA15288@namesys.com> (raw)
In-Reply-To: <20030815121321.49e4cf09.skraw@ithnet.com>

Hello!

On Fri, Aug 15, 2003 at 12:13:21PM +0200, Stephan von Krawczynski wrote:

> there was a question about fsck'ing the ext3 filesystems. Since it crashed
> today I did check them now and no errors or warnings showed up. Everything
> seems clean. I don't exactly understand what that tells you. I guess you mean
> the fs metadata may have been hit, too. Seems not.

Yes. And from what I remember, all the oopses on reiserfs were about some
lists corruptions and this sort of things, so not metadata, but kernel
data was damaged somehow.
And your last oops confirms that.
end_buffer_io_async have the loop running with irqs disabled.
And this loop in your case should only have one iteration (you run with 4k
blocksize, I presume) of gouig thorough one buffer attaching to a page.
Also at least one of the oopses you posted prior to that also had signs of
buffer list corruptions. (may be even two).
So it seems something changes buffer lists under out feet without doing
proper locking.
I am not sure how this relates to data corruption, though.
Ok, at least now there seems to be something definite to look for in changes.

Thank you.

Bye,
    Oleg

  reply	other threads:[~2003-08-15 10:31 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030808002918.723abb08.skraw@ithnet.com>
2003-08-08 14:54 ` 2.4.22-pre lockups (now decoded oops for pre10) Marcelo Tosatti
2003-08-08 15:05   ` Stephan von Krawczynski
2003-08-08 15:33     ` Marcelo Tosatti
2003-08-10 21:35       ` Stephan von Krawczynski
2003-08-10 23:23         ` Neil Brown
2003-08-11  9:33           ` Stephan von Krawczynski
2003-08-18 20:43             ` Mike Fedyk
2003-08-13 10:55       ` Stephan von Krawczynski
2003-08-13 14:53         ` Marcelo Tosatti
2003-08-13 14:59           ` Oleg Drokin
2003-08-13 15:12             ` Stephan von Krawczynski
2003-08-13 15:30               ` Oleg Drokin
2003-08-13 16:04                 ` Stephan von Krawczynski
2003-08-13 16:34                   ` Oleg Drokin
2003-08-13 22:19                     ` Stephan von Krawczynski
2003-08-14  8:45                       ` Oleg Drokin
2003-08-14 17:26                         ` Marcelo Tosatti
2003-08-14 17:42                           ` Stephan von Krawczynski
2003-08-15  2:08                             ` Chris Mason
2003-08-15  9:40                               ` Stephan von Krawczynski
2003-08-15 10:28                               ` Stephan von Krawczynski
2003-08-15 12:55                                 ` Chris Mason
2003-08-20 14:21                                   ` 2.4.22-pre lockups (yet another oops for rc2) Stephan von Krawczynski
2003-09-05  9:24                                   ` 2.4.22-pre lockups (case closed) Stephan von Krawczynski
2003-09-05 13:37                                     ` Andrea Arcangeli
2003-08-15 10:13                         ` 2.4.22-pre lockups (now decoded oops for pre10) Stephan von Krawczynski
2003-08-15 10:31                           ` Oleg Drokin [this message]
2003-08-18 15:06                   ` Andrea Arcangeli
2003-08-18 20:19                     ` Stephan von Krawczynski
2003-08-18 20:58                       ` Mike Fedyk
2003-08-18 22:31                       ` Andrea Arcangeli
2003-08-19  1:12                         ` Mike Fedyk
2003-08-19  7:12                           ` Stephan von Krawczynski
2003-08-19 13:10                             ` Alan Cox
2003-08-19 14:18                               ` Stephan von Krawczynski
2003-08-19 18:00                                 ` Mike Fedyk
2003-08-19 21:58                                   ` Stephan von Krawczynski
2003-08-19 13:27                             ` Andrea Arcangeli
2003-08-13 15:21           ` Jim Gifford
2003-08-13 17:08             ` Marcelo Tosatti
2003-08-10 14:23     ` Keith Owens
2003-08-02 12:27 2.4.22-pre lockups (decoded oops for pre8) Stephan von Krawczynski
2003-08-05 16:40 ` Marcelo Tosatti
2003-08-06  7:41   ` 2.4.22-pre lockups (now decoded oops for pre10) Stephan von Krawczynski
2003-08-06  8:58     ` Oleg Drokin
2003-08-06  9:09     ` Willy Tarreau
2003-08-06  9:36       ` Stephan von Krawczynski
2003-08-06 12:45         ` Willy Tarreau
2003-08-18 14:23       ` Andrea Arcangeli
2003-08-06 18:15     ` Marcelo Tosatti
2003-08-07  2:14       ` Stephan von Krawczynski
2003-08-07  5:35         ` Oleg Drokin
2003-08-07 12:45         ` Marcelo Tosatti
     [not found]           ` <3F325198.2010301@namesys.com>
2003-08-07 13:32             ` Stephan von Krawczynski
2003-08-18 20:29               ` Mike Fedyk
2003-08-18 20:39                 ` Stephan von Krawczynski
2003-08-18 21:09                   ` Mike Fedyk
2003-08-07 15:52           ` Stephan von Krawczynski

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=20030815103104.GA15288@namesys.com \
    --to=green@namesys.com \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=andrea@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=mason@suse.com \
    --cc=skraw@ithnet.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox