From: Linus Torvalds <torvalds@transmeta.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Stephen C. Tweedie" <sct@redhat.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Ben LaHaise <bcrl@redhat.com>, Christoph Rohland <cr@sap.com>
Subject: Re: [PATCH] Fix races in 2.4.2-ac22 SysV shared memory
Date: Fri, 23 Mar 2001 14:37:21 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.31.0103231435000.766-100000@penguin.transmeta.com> (raw)
In-Reply-To: <E14ga9U-0005aa-00@the-village.bc.nu>
On Fri, 23 Mar 2001, Alan Cox wrote:
>
> __find_get_page has I think a misleading comment ?
Ehh..
I only said the _naming_ makes sense. [ Wild hand-waving ]
I suspect that what happened was that we split off the functions (one to
just get the page, one to lock it), and the comment that was associated
with the original "find_page()" never got removed, and just happens to sit
above one of the helper functions now - the one that didn't lock.
I'll fix the comment.
Linus
--
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.eu.org/Linux-MM/
next prev parent reply other threads:[~2001-03-23 22:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-23 1:13 Stephen C. Tweedie
2001-03-23 19:58 ` Linus Torvalds
2001-03-23 22:20 ` Alan Cox
2001-03-23 22:23 ` Alexander Viro
2001-03-23 22:29 ` Alan Cox
2001-03-23 22:27 ` Linus Torvalds
2001-03-23 22:35 ` Alan Cox
2001-03-23 22:37 ` Linus Torvalds [this message]
2001-03-23 22:31 ` David S. Miller
2001-03-25 0:13 ` Stephen C. Tweedie
2001-03-25 1:05 ` Rik van Riel
2001-03-25 16:50 ` Stephen C. Tweedie
2001-03-28 9:18 ` Christoph Rohland
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=Pine.LNX.4.31.0103231435000.766-100000@penguin.transmeta.com \
--to=torvalds@transmeta.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bcrl@redhat.com \
--cc=cr@sap.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sct@redhat.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