From: "Ingo Bormuth" <ibormuth@efil.de>
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: Tue, 27 Jan 2009 11:02:01 +0100 [thread overview]
Message-ID: <1233050521.11907.6.camel@localhost> (raw)
In-Reply-To: <200901251813.50957.volkerarmin@googlemail.com>
[-- Attachment #1: Type: text/plain, Size: 574 bytes --]
On Sun, 2009-01-25 at 18:13 +0100, Volker Armin Hemmann wrote:
> so without Ingo Bormuth's patch you can't use r4 with 2.6.28.1 and later and
> with his patch there is a risk of deadlocks?
After Edward's reply actually I changed to use the attached mm patch
which is actually the same as what I did with additionally setting the
AOP_FLAG_NOFS flag before calling grab_cache_page_write_begin. It
applies and works nicely with vanilla 2.6.28.2 too.
--
Ingo Bormuth, voicebox & telefax: +49-(0)-12125-10226517
PGP public key 86326EC9 at http://ibormuth.efil.de/contact
[-- Attachment #2: fs-symlink-write_begin-allocation-context-fix-reiser4-fix.patch --]
[-- Type: text/x-patch, Size: 936 bytes --]
From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
build fix.
Signed-off-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Nick Piggin <npiggin@suse.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
fs/reiser4/plugin/file/file_conversion.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff -puN fs/reiser4/plugin/file/file_conversion.c~fs-symlink-write_begin-allocation-context-fix-reiser4-fix fs/reiser4/plugin/file/file_conversion.c
--- a/fs/reiser4/plugin/file/file_conversion.c~fs-symlink-write_begin-allocation-context-fix-reiser4-fix
+++ a/fs/reiser4/plugin/file/file_conversion.c
@@ -686,7 +686,8 @@ int reiser4_write_begin_careful(struct f
start = pos & (PAGE_CACHE_SIZE - 1);
end = start + len;
- page = __grab_cache_page(mapping, index);
+ page = grab_cache_page_write_begin(mapping, index,
+ flags & AOP_FLAG_NOFS);
*pagep = page;
if (!page)
return -ENOMEM;
_
next prev parent reply other threads:[~2009-01-27 10:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-19 0:53 Reiser4: Compilation Error on 2.6.28.1_[Scanned] Ingo Bormuth
2009-01-19 21:27 ` Edward Shishkin
2009-01-25 17:13 ` Volker Armin Hemmann
2009-01-27 10:02 ` Ingo Bormuth [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-01-25 17:15 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
2009-01-25 17:52 ` Teran McKinney
2009-01-25 17:56 ` Volker Armin Hemmann
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=1233050521.11907.6.camel@localhost \
--to=ibormuth@efil.de \
--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