All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Mark Fasheh <mark.fasheh@oracle.com>
Cc: Linux Memory Management <linux-mm@kvack.org>,
	linux-fsdevel@vger.kernel.org,
	linux-kernel <linux-kernel@vger.kernel.org>,
	OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
	Andrew Morton <akpm@google.com>
Subject: Re: Status of buffered write path (deadlock fixes)
Date: Tue, 12 Dec 2006 01:20:52 +1100	[thread overview]
Message-ID: <457D6944.4010703@yahoo.com.au> (raw)
In-Reply-To: <457D20AE.6040107@yahoo.com.au>

Nick Piggin wrote:
> Mark Fasheh wrote:

>> If we make the change I described above (looking for BH_New buffers 
>> outside
>> the range passed), then zero length or partial shouldn't matter, but zero
>> length instead of partial would be nicer imho just for the sake of 
>> reducing
>> the total number of cases down to the entire range or zero length.
> 
> 
> We don't want to do zero length, because we might make the theoretical
> livelock much easier to hit (eg. in the case of many small iovecs). But
> yes we can restrict ourselves to zero-length or full-length.

On second thoughts, I think I'm wrong about that.

Consider the last page of a file, which is uptodate. A full length
commit, which extends the file, will expose transient zeroes if the
usercopy fails.

-- 
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com 

WARNING: multiple messages have this Message-ID (diff)
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Mark Fasheh <mark.fasheh@oracle.com>
Cc: Linux Memory Management <linux-mm@kvack.org>,
	linux-fsdevel@vger.kernel.org,
	linux-kernel <linux-kernel@vger.kernel.org>,
	OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
	Andrew Morton <akpm@google.com>
Subject: Re: Status of buffered write path (deadlock fixes)
Date: Tue, 12 Dec 2006 01:20:52 +1100	[thread overview]
Message-ID: <457D6944.4010703@yahoo.com.au> (raw)
In-Reply-To: <457D20AE.6040107@yahoo.com.au>

Nick Piggin wrote:
> Mark Fasheh wrote:

>> If we make the change I described above (looking for BH_New buffers 
>> outside
>> the range passed), then zero length or partial shouldn't matter, but zero
>> length instead of partial would be nicer imho just for the sake of 
>> reducing
>> the total number of cases down to the entire range or zero length.
> 
> 
> We don't want to do zero length, because we might make the theoretical
> livelock much easier to hit (eg. in the case of many small iovecs). But
> yes we can restrict ourselves to zero-length or full-length.

On second thoughts, I think I'm wrong about that.

Consider the last page of a file, which is uptodate. A full length
commit, which extends the file, will expose transient zeroes if the
usercopy fails.

-- 
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com 

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2006-12-11 14:21 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-05  6:52 Status of buffered write path (deadlock fixes) Nick Piggin
2006-12-05  6:52 ` Nick Piggin
2006-12-07 19:55 ` Mark Fasheh
2006-12-07 19:55   ` Mark Fasheh
2006-12-08  3:28   ` Nick Piggin
2006-12-08  3:28     ` Nick Piggin
2006-12-08 23:48     ` Mark Fasheh
2006-12-08 23:48       ` Mark Fasheh
2006-12-11  9:11       ` Nick Piggin
2006-12-11  9:11         ` Nick Piggin
2006-12-11 14:20         ` Nick Piggin [this message]
2006-12-11 14:20           ` Nick Piggin
2006-12-11 15:52         ` Nick Piggin
2006-12-11 15:52           ` Nick Piggin
2006-12-11 16:12           ` Steven Whitehouse
2006-12-11 16:39             ` Nick Piggin
2006-12-11 16:39               ` Nick Piggin
2006-12-11 17:18               ` Steven Whitehouse
2006-12-11 17:18                 ` Steven Whitehouse
2006-12-12 22:31           ` Mark Fasheh
2006-12-12 22:31             ` Mark Fasheh
2006-12-13  0:53             ` Nick Piggin
2006-12-13  0:53               ` Nick Piggin
2006-12-13  1:47               ` Trond Myklebust
2006-12-13  1:47                 ` Trond Myklebust
2006-12-13  1:56                 ` Nick Piggin
2006-12-13  1:56                   ` Nick Piggin
2006-12-13  2:31                   ` Trond Myklebust
2006-12-13  2:31                     ` Trond Myklebust
2006-12-13  4:03                     ` Nick Piggin
2006-12-13  4:03                       ` Nick Piggin
2006-12-13 12:21                       ` Trond Myklebust
2006-12-13 12:21                         ` Trond Myklebust
2006-12-13 13:49                     ` Peter Staubach
2006-12-13 13:49                       ` Peter Staubach
2006-12-13 13:55                       ` Trond Myklebust
2006-12-13 13:55                         ` Trond Myklebust
2006-12-11 18:17 ` OGAWA Hirofumi
2006-12-11 18:17   ` OGAWA Hirofumi

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=457D6944.4010703@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=akpm@google.com \
    --cc=hirofumi@mail.parknet.co.jp \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mark.fasheh@oracle.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.