All of lore.kernel.org
 help / color / mirror / Atom feed
From: Edward Shishkin <edward.shishkin@gmail.com>
To: Volker Armin Hemmann <volkerarmin@googlemail.com>
Cc: reiserfs-devel@vger.kernel.org
Subject: Re: Reiser4: Compilation Error on 2.6.28.1_[Scanned]
Date: Sun, 25 Jan 2009 20:44:17 +0300	[thread overview]
Message-ID: <497CA4F1.3050807@gmail.com> (raw)
In-Reply-To: <200901251837.58313.volkerarmin@googlemail.com>

Volker Armin Hemmann wrote:
> On Sonntag 25 Januar 2009, Edward Shishkin wrote:
>   
>> Volker Armin Hemmann wrote:
>>     
>>> On Montag 19 Januar 2009, Edward Shishkin wrote:
>>>       
>>>> Ingo Bormuth wrote:
>>>>         
>>>>> Reiser4-for-2.6.28 does apply but fails to compile on
>>>>> vanilla-2.6.28.1 due to the following commit:
>>>>>
>>>>> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=comm
>>>>> it diff;h=54566b2c1594c2326a645a3551f9d989f7ba3c5e
>>>>>
>>>>> Attached is a tiny fix which works fine here.
>>>>>           
>>>> yeah, with your patch it will act as earlier,
>>>> however, -mm guys decided to get rig of __GFP_FS flag:
>>>> http://userweb.kernel.org/~akpm/mmotm/broken-out/fs-symlink-write_begin-
>>>> all ocation-context-fix-reiser4-fix.patch it seems they found it
>>>> deadlocky..
>>>>         
>>> so without Ingo Bormuth's patch you can't use r4 with 2.6.28.1
>>>       
>> Ingo's patch is against -rc
>>
>>     
>>>  and later and
>>> with his patch there is a risk of deadlocks?
>>>       
>> Not sure.
>> Nobody complained so far..
>>     
>
> hm, I had two lockups with 2.6.28 and your r4 patch so far. Suddenly the box 
> only responded to sysrq

Would you please send the sysrq-t output?

 
>  - and on reboot the software raid5 with my r4 
> partitions on needed a resync. Might be related or not. I am back to 2.6.27 
> which never showed any misbehaviour.
>
> Glück Auf,
> Volker
>
>
>   

--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2009-01-25 17:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-25 17:15 Reiser4: Compilation Error on 2.6.28.1_[Scanned] Volker Armin Hemmann
2009-01-25 17:32 ` Edward Shishkin
2009-01-25 17:37   ` Volker Armin Hemmann
2009-01-25 17:44     ` Edward Shishkin [this message]
2009-01-25 17:52       ` Teran McKinney
2009-01-25 17:56       ` Volker Armin Hemmann
  -- strict thread matches above, loose matches on Subject: below --
2009-01-19  0:53 Ingo Bormuth
2009-01-19 21:27 ` Edward Shishkin
2009-01-25 17:13   ` Volker Armin Hemmann
2009-01-27 10:02     ` Ingo Bormuth

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=497CA4F1.3050807@gmail.com \
    --to=edward.shishkin@gmail.com \
    --cc=reiserfs-devel@vger.kernel.org \
    --cc=volkerarmin@googlemail.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.