public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Hugh Dickins <hugh@veritas.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>, Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, pavel@suse.cz
Subject: Re: [PATCH -mm] swsusp: support creating bigger images
Date: Wed, 10 May 2006 13:50:57 +1000	[thread overview]
Message-ID: <44616321.2000404@yahoo.com.au> (raw)
In-Reply-To: <Pine.LNX.4.64.0605091301140.21281@blonde.wat.veritas.com>

Hugh Dickins wrote:

>On Tue, 9 May 2006, Rafael J. Wysocki wrote:
>
>>On Tuesday 09 May 2006 09:33, Andrew Morton wrote:
>>    
>>
>>>task_struct.mm can sometimes be NULL.  This function assumes that it will
>>>never be NULL.  That makes it a somewhat risky interface.  Are we sure it
>>>can never be NULL?
>>>
>>Well, now it's only called for task == current, but I can add a check.
>>
>
>Better fold it into the (renamed and recommented) page_to_copy,
>applying only to current.
>
>The "use" of page_table_lock there is totally bogus.  Normally you
>need down_read(&current->mm->mmap_sem) to walk that vma chain; but
>I'm guessing you have everything sufficiently frozen here that you
>don't need that.
>

I have to admit that I suggested making this change, because the
function was sufficently generic looking. I guess the mm == NULL
case should logically return 0... unless you did that, making
page_mapped_by_task use current still leaves the burden of ensuring
->mm != NULL on the caller.

But I don't much mind which way the consensus goes.

---

Send instant messages to your online friends http://au.messenger.yahoo.com 

  reply	other threads:[~2006-05-10  3:51 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-02 10:00 [PATCH -mm] swsusp: support creating bigger images Rafael J. Wysocki
2006-05-09  7:33 ` Andrew Morton
2006-05-09 10:19   ` Rafael J. Wysocki
2006-05-09 11:22     ` Pavel Machek
2006-05-09 12:18       ` Rafael J. Wysocki
2006-05-09 12:30     ` Hugh Dickins
2006-05-10  3:50       ` Nick Piggin [this message]
2006-05-10 22:26       ` Rafael J. Wysocki
2006-05-11 15:01         ` Hugh Dickins
2006-05-11 21:19           ` Rafael J. Wysocki
2006-05-09 22:15     ` [PATCH -mm] swsusp: support creating bigger images (rev. 2) Rafael J. Wysocki
2006-05-09 22:27       ` Andrew Morton
2006-05-10 22:58         ` Rafael J. Wysocki
2006-05-10 23:38           ` Andrew Morton
2006-05-11  0:11             ` Nigel Cunningham
2006-05-11 13:20               ` Rafael J. Wysocki
2006-05-11 23:45                 ` Nigel Cunningham
2006-05-12  0:17                   ` Nathan Scott
2006-05-12 10:09                     ` Pavel Machek
2006-05-13 22:32                   ` Rafael J. Wysocki
2006-05-11 13:15             ` Rafael J. Wysocki
2006-05-11 11:35           ` Pavel Machek
2006-05-11 12:10             ` Rafael J. Wysocki
2006-05-11 23:49             ` Nigel Cunningham
2006-05-12 10:30               ` Pavel Machek
2006-05-13 22:33                 ` Rafael J. Wysocki
2006-05-15  9:48                   ` Con Kolivas
2006-05-15 19:52                     ` Rafael J. Wysocki
2006-05-15 23:50                       ` Con Kolivas

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=44616321.2000404@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=akpm@osdl.org \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    --cc=rjw@sisk.pl \
    /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