mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mathieu Segaud <matt@minas-morgul.org>
To: Vladimir Saveliev <vs@namesys.com>
Cc: reiserfs-list@namesys.com,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: 2.6.10-rc2-mm1: oops when accessing reiser4 fs's (maybe fix provided)
Date: Wed, 17 Nov 2004 17:55:51 +0100	[thread overview]
Message-ID: <87d5ycza7c.fsf@barad-dur.crans.org> (raw)
In-Reply-To: <1100675389.1399.27.camel@tribesman.namesys.com> (Vladimir Saveliev's message of "Wed, 17 Nov 2004 10:09:49 +0300")

Vladimir Saveliev <vs@namesys.com> disait dernièrement que :

> Hello
>
> On Tue, 2004-11-16 at 21:53, Mathieu Segaud wrote:
>> I tried 2.6.10-rc2-mm1 and the last reiser4 updates gave some (many many)
>> oopses flooding my screen :).
>> I tried reverting reiser4-fix-deadlock.patch and oopses are gone.
>> 
> Would you please instead try the attached patch? 

yep.
indeed it worked
anyway, for the quick answer

>
>> I tried this one because thru the quick traces on my screen, I saw a reference
>> to get_current_context.
>> The speed of the traces and the unasibility of the box prevented me from
>> making differences between "real" oopses and BUG_ON(), sorry for that...
>> 
>> If you want some traces I can provide them ASAP (e.g. tomorrow)
>
>
>
>

-- 
Carrots work on rabbits, they don't work on hungry weasels.

	- Alan Cox on linux-kernel


      reply	other threads:[~2004-11-17 16:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-16 18:53 Mathieu Segaud
2004-11-17  7:09 ` Vladimir Saveliev
2004-11-17 16:55   ` Mathieu Segaud [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=87d5ycza7c.fsf@barad-dur.crans.org \
    --to=matt@minas-morgul.org \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiserfs-list@namesys.com \
    --cc=vs@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 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®