From: ebiederm+eric@ccr.net (Eric W. Biederman)
To: linux-mm@kvack.org
Cc: Hans Eric Sandstrom <hes@xinit.se>
Subject: Re: Beta quality write out daemon
Date: 17 Jan 1999 23:05:23 -0600 [thread overview]
Message-ID: <m1sod9dvcc.fsf@flinx.ccr.net> (raw)
In-Reply-To: ebiederm+eric@ccr.net's message of "17 Jan 1999 00:12:25 -0600"
>>>>> "EB" == Eric W Biederman <ebiederm> writes:
EB> I also seem to have detected a bug in some other part of the kernel.
EB> Where I can find a dirty pte pointing to a swap cache page.
Looking further it's a bug but an unexpected feature.
I thought the invariant that there could be only 1 mapping of a
of a writeable swappable page. Would lead to the invariant that
for a writeable swappable page there can be only one dirty page table entry.
When fork does it's Copy On Write split it write protects both the old
and the new page table entries but it leaves both it leaves the dirty bit
set in both of them. Which really is correct behavior. Just totally unexpected.
It's taken forever to track this down. But I at least now that it is
I can move forward.
Eric
--
This is a majordomo managed list. To unsubscribe, send a message with
the body 'unsubscribe linux-mm me@address' to: majordomo@kvack.org
next prev parent reply other threads:[~1999-01-18 9:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-14 10:08 Alpha " Eric W. Biederman
[not found] ` <369E0501.987D2B3B@xinit.se>
1999-01-14 16:49 ` Eric W. Biederman
1999-01-15 7:31 ` Eric W. Biederman
1998-01-14 18:44 ` Hans Eric Sandström
1999-01-15 9:02 ` Eric W. Biederman
1999-01-17 6:12 ` Beta " Eric W. Biederman
1999-01-18 5:05 ` Eric W. Biederman [this message]
1999-01-19 15:15 ` Alpha " Stephen C. Tweedie
1999-01-20 14:52 ` Eric W. Biederman
1999-01-20 18:46 ` Zlatko Calusic
1999-01-25 1:40 ` Eric W. Biederman
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=m1sod9dvcc.fsf@flinx.ccr.net \
--to=ebiederm+eric@ccr.net \
--cc=hes@xinit.se \
--cc=linux-mm@kvack.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