Linux ReiserFS filesystem (obsolete)
 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:32:37 +0300	[thread overview]
Message-ID: <497CA235.9030504@gmail.com> (raw)
In-Reply-To: <200901251815.08030.volkerarmin@googlemail.com>

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=commit
>>> 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..

Edward.

  reply	other threads:[~2009-01-25 17:32 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 [this message]
2009-01-25 17:37   ` Volker Armin Hemmann
2009-01-25 17:44     ` Edward Shishkin
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=497CA235.9030504@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox