From: "Mark F. Haigh" <Mark.Haigh@spirentcom.com>
To: Chris Wright <chrisw@osdl.org>
Cc: linux-security-module@wirex.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kernel/fork.c: VM accounting bugfix (2.6.11-rc3-bk5)
Date: Wed, 09 Feb 2005 12:04:10 -0800 [thread overview]
Message-ID: <420A6CBA.3050308@spirentcom.com> (raw)
In-Reply-To: <20050208230447.V24171@build.pdx.osdl.net>
Chris Wright wrote:
<snip>
>
> You missed one subtle point. That failure case actually unaccts 0 pages
> (note the use of charge). Not the nicest, but I believe correct.
>
Right. I did miss that. Thanks for the explanations, Chris and Hugh, I
appreciate it.
Mark F. Haigh
Mark.Haigh@spirentcom.com
next prev parent reply other threads:[~2005-02-09 20:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-09 3:51 [PATCH] kernel/fork.c: VM accounting bugfix (2.6.11-rc3-bk5) Mark F. Haigh
2005-02-09 7:04 ` Chris Wright
2005-02-09 12:30 ` Hugh Dickins
2005-02-09 19:28 ` Chris Wright
2005-02-09 19:46 ` Hugh Dickins
2005-02-09 20:04 ` Mark F. Haigh [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-02-09 3:48 Mark F. Haigh
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=420A6CBA.3050308@spirentcom.com \
--to=mark.haigh@spirentcom.com \
--cc=chrisw@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@wirex.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