linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Andrew Morton <akpm@osdl.org>, Hugh Dickins <hugh@veritas.com>,
	LKML <linux-kernel@vger.kernel.org>,
	fsdevel <linux-fsdevel@vger.kernel.org>,
	lee.schermerhorn@hp.com,
	Reiserfs developers mail-list <Reiserfs-Dev@namesys.com>
Subject: Re: Fw: Re: [PATCH] 2.6.16-rc-mm4 reiser4 calls try_to_unmap() with 1 arg -- now takes 2
Date: Sun, 05 Feb 2006 00:45:34 -0800	[thread overview]
Message-ID: <43E5BB2E.5000203@namesys.com> (raw)
In-Reply-To: <20060205003039.3067e43c.akpm@osdl.org>

Umm, no, copy on capture needs to get enabled again as soon as we get
past issues outsiders care about, and start dealing again with improving
the code in the ways we think matter.  There are real problems that are
addressed by copy on capture.  That it has not been worked on since
2.6.5 just sadly indicates how successful folks have been in distracting
us for so long.

vs, open a bug report in bugzilla for copy on capture, and after we get
merged please make copy on capture work. 

Hans

Andrew Morton wrote:

>Hugh's right - quite worrying..
>
>Begin forwarded message:
>
>Date: Thu, 2 Feb 2006 20:46:07 +0000 (GMT)
>From: Hugh Dickins <hugh@veritas.com>
>To: Lee Schermerhorn <lee.schermerhorn@hp.com>
>Cc: linux-kernel <linux-kernel@vger.kernel.org>, linux-fsdevel@vger.kernel.org
>Subject: Re: [PATCH] 2.6.16-rc-mm4 reiser4 calls try_to_unmap() with 1 arg -- now takes 2
>
>
>On Thu, 2 Feb 2006, Lee Schermerhorn wrote:
>
>  
>
>>Apparent race between reiser4 and direct migration patches in 16-rc1-
>>mm4.
>>Direct migration added arg to rmap.c:try_to_unmap()--int ignore_refs--
>>and
>>fixed up existing refs.  reiser4 adds new call with single arg. 
>>
>>One doesn't see this when building mm4 w/ reiser4 because the ref under
>>an
>>"#if REISER4_COPY_ON_CAPTURE" that is apparently not enabled.  I  just
>>noticed
>>it while looking at direct migration patches.  So, this patch is
>>essentially
>>UNTESTED.  Supplied simply to illustrate the location of the single arg
>>    
>>
>
>That's worrying code to find down in a filesystem.  But never mind,
>it refers to pte_chain_lock(), which hasn't existed since 2.6.5.  So
>REISER4_COPY_ON_CAPTURE is long untested and should just be deleted.
>
>Hugh
>
>  
>
>>Signed-off-by: Lee Schermerhorn <lee.schermerhorn@hp.com>
>>
>>Index: linux-2.6.16-rc1-mm4/fs/reiser4/txnmgr.c
>>===================================================================
>>--- linux-2.6.16-rc1-mm4.orig/fs/reiser4/txnmgr.c	2006-01-31
>>16:51:39.000000000 -0500
>>+++ linux-2.6.16-rc1-mm4/fs/reiser4/txnmgr.c	2006-02-02
>>14:43:01.659744418 -0500
>>@@ -3693,7 +3693,7 @@ static int create_copy_and_replace(jnode
>> 		pte_chain_lock(page);
>> 
>> 		if (page_mapped(page)) {
>>-			result = try_to_unmap(page);
>>+			result = try_to_unmap(page, 0);
>> 			if (result == SWAP_AGAIN) {
>> 				result = RETERR(-E_REPEAT);
>>    
>>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at  http://www.tux.org/lkml/
>
>
>  
>


       reply	other threads:[~2006-02-05  8:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060205003039.3067e43c.akpm@osdl.org>
2006-02-05  8:45 ` Hans Reiser [this message]
2006-02-05  9:11   ` Fw: Re: [PATCH] 2.6.16-rc-mm4 reiser4 calls try_to_unmap() with 1 arg -- now takes 2 Andrew Morton
2006-02-05 18:42     ` Hans Reiser

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=43E5BB2E.5000203@namesys.com \
    --to=reiser@namesys.com \
    --cc=Reiserfs-Dev@namesys.com \
    --cc=akpm@osdl.org \
    --cc=hugh@veritas.com \
    --cc=lee.schermerhorn@hp.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).