All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vince <fuzzy77@laposte.net>
To: "Vladimir V. Saveliev" <vs@namesys.com>
Cc: reiserfs-list@namesys.com, Andrew Morton <akpm@osdl.org>,
	Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: linux-2.6.20-rc4-mm1 Reiser4 filesystem freeze and corruption
Date: Thu, 25 Jan 2007 08:33:28 +0100	[thread overview]
Message-ID: <45B85D48.9080403@laposte.net> (raw)
In-Reply-To: <200701232215.37321.vs@namesys.com>

Vladimir V. Saveliev wrote:
> Hello
> 
> On Tuesday 23 January 2007 10:38, Vince wrote:
[...]
>> I don't know if it is related, but I've had the following BUG on 
>> 2.6.20-rc4-mm1 (+ hot-fixes patches applied) :
>>
>> -------------------
>> kernel BUG at fs/reiser4/plugin/item/extent_file_ops.c:973!
> 
> This is another problem than Zan's one. The attached patch should fix it.
> 
> Andrew, please apply.
> 
> 
> From: Vladimir Saveliev <vs@namesys.com>
> 
> remove_suid may open a transaction in reiser4 which is to be restarted
> before entering into main write loop.
> 
> Signed-off-by: Vladimir Saveliev <vs@namesys.com>

I'm pleased to confirm I wasn't able to reproduce the bug with your 
patch applied.

Regards,

Vince

      reply	other threads:[~2007-01-25  7:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-19 17:58 linux-2.6.20-rc4-mm1 Reiser4 filesystem freeze and corruption Zan Lynx
2007-01-19 18:53 ` Edward Shishkin
2007-01-20  0:34 ` Vladimir V. Saveliev
2007-01-31 18:13   ` Zan Lynx
2007-02-01 15:54     ` Edward Shishkin
2007-02-02  0:21       ` Zan Lynx
2007-01-22 15:48 ` reiserfs4 primary contact Timothy Webster
2007-01-22 17:08   ` Vladimir V. Saveliev
2007-01-23  7:38 ` linux-2.6.20-rc4-mm1 Reiser4 filesystem freeze and corruption Vince
2007-01-23 19:15   ` Vladimir V. Saveliev
2007-01-25  7:33     ` Vince [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=45B85D48.9080403@laposte.net \
    --to=fuzzy77@laposte.net \
    --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 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.