9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] kernel bug
Date: Tue,  3 Jun 2014 11:47:07 -0400	[thread overview]
Message-ID: <d3a17694dd714f53054031e9ac67dd35@mikro.quanstro.net> (raw)
In-Reply-To: <C29EB1DC-4A22-4149-9510-3054933D77C5@fb.com>

> I think it should be
> if(mapsize > (SEGMAPSIZE))
>             mapsize = SEGMAPSIZE;

hmm.  i think this code is correct.  ssegmap is a static map
to handle small segments.  small segments fit in ssegmap.
the point must have been to avoid malloc.

this test is a little more questionable

>	if(mapsize > (SEGMAPSIZE*PTEPERTAB))
>		mapsize = (SEGMAPSIZE*PTEPERTAB);

cf. the check in ibrk

	if(newsize > (SEGMAPSIZE*PTEPERTAB)) {
		qunlock(&s->lk);
		error(Enovmem);
	}

i think this check is either not wrong, or more extensive rework
is necessary.

@anthony, do you know if this code or similar occurred in even older kernels?
if there was a cap also in ibrk() then i would suspect this code was originally
correct.

i don't know where a history of stuff older than sources (2002) is.

> Also why in the kernel they use 'struct Pte' instead of the better name Pagetable.
> In many places this is very confusing because when I see Pte I think of a Pagetable Entry
> where really they are speaking about a Pagetable.

i would naturally think a Pte* would be an array of Pte's, i.e. a Pte table,
just like an array of uchar* could be used as a table.

- erik



  parent reply	other threads:[~2014-06-03 15:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-03  1:14 Yoann Padioleau
2014-06-03  5:49 ` cinap_lenrek
2014-06-03  6:00 ` Anthony Martin
2014-06-03 15:47 ` erik quanstrom [this message]
2014-06-03 15:56   ` andrey mirtchovski
2014-06-03 16:04     ` erik quanstrom
2014-06-04 19:12   ` Anthony Martin
2014-06-03 16:08 ` Charles Forsyth
2014-06-03 17:08   ` erik quanstrom
2014-06-03 18:04     ` Charles Forsyth
2014-06-03 18:09       ` Charles Forsyth

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=d3a17694dd714f53054031e9ac67dd35@mikro.quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@9fans.net \
    /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;
as well as URLs for NNTP newsgroup(s).