All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Łukasz Mierzwa" <prymitive@pcserwis.net>
To: Alexander Zarochentsev <zam@namesys.com>,
	"reiserfs-list@namesys.com" <reiserfs-list@namesys.com>
Subject: Re: reiser4 for 2.6.13 is available on our website
Date: Fri, 30 Sep 2005 14:01:16 +0200	[thread overview]
Message-ID: <op.sxwzoenad4os1z@localhost> (raw)
In-Reply-To: <200509301231.02169.zam@namesys.com>

Dnia Fri, 30 Sep 2005 10:31:01 +0200, Alexander Zarochentsev  
<zam@namesys.com> napisa³:

> On Friday 30 September 2005 02:09, Jake Maciejewski wrote:
>> I get the same with 2.6.13.2 and gcc 3.4.4 on amd64
>>
> can you try this patch?
> -----------------------------------
> --- a/fs/reiser4/spin_macros.h
> +++ b/fs/reiser4/spin_macros.h
> @@ -82,8 +82,6 @@ typedef struct reiser4_rw_data {
>  static inline void spin_ ## NAME ## _init(TYPE *x)				\
>  {										\
>  	__ODCA("nikita-2987", x != NULL);					\
> -	cassert(sizeof(x->FIELD) != 0);						\
> -	memset(& x->FIELD, 0, sizeof x->FIELD);					\
>  	spin_lock_init(& x->FIELD.lock);					\
>  }										\
>  										\
> @@ -236,7 +234,6 @@ typedef struct { int foo; } NAME ## _spi
>  static inline void rw_ ## NAME ## _init(TYPE *x)				\
>  {										\
>  	__ODCA("nikita-2988", x != NULL);					\
> -	memset(& x->FIELD, 0, sizeof x->FIELD);					\
>  	rwlock_init(& x->FIELD.lock);						\
>  }										\
>  										\
> -----------------------------------

It helped (cut and paste didn't worked for me as the resulting patch  
didn't applied but I just deleted those 3 lines by hand). Kernel did  
compile and now I'm writing this running 2.6.13 with reiser4 as /. I hope  
I won't see any oopses during shutdown as I sow with 2.6.13-mm{1,2} based  
kernels (archck).


  reply	other threads:[~2005-09-30 12:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-29 17:25 reiser4 for 2.6.13 is available on our website Hans Reiser
2005-09-29 18:24 ` Łukasz Mierzwa
2005-09-29 22:09   ` Jake Maciejewski
2005-09-29 22:32     ` Hans Reiser
2005-09-29 23:23       ` Gregory Maxwell
2005-09-30  2:59         ` Dan Oglesby
2005-09-30  3:03           ` Dan Oglesby
2005-09-30  5:02             ` Dan Oglesby
2005-09-30  6:01               ` Dan Oglesby
2005-09-30  8:31     ` Alexander Zarochentsev
2005-09-30 12:01       ` Łukasz Mierzwa [this message]
2005-10-01  7:20       ` Jake Maciejewski

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=op.sxwzoenad4os1z@localhost \
    --to=prymitive@pcserwis.net \
    --cc=reiserfs-list@namesys.com \
    --cc=zam@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.