From: Herbert Valerio Riedel <hvr@hvrlab.org>
To: Dan Malek <dan@embeddededge.com>
Cc: Josh Green <jgreen@users.sourceforge.net>,
linux-mips@linux-mips.org, Pete Popov <ppopov@embeddedalley.com>
Subject: Re: iptables/vmalloc issues on alchemy
Date: Thu, 28 Apr 2005 07:06:52 +0200 [thread overview]
Message-ID: <1114664812.4647.6.camel@mini.intra> (raw)
In-Reply-To: <4bf8c757c3a4d32177ab90b92eace823@embeddededge.com>
On Wed, 2005-04-27 at 15:06 -0400, Dan Malek wrote:
> On Apr 27, 2005, at 2:49 PM, Josh Green wrote:
>
> > ...... I was
> > planning on doing some additional gdb debugging of the failure
> > (especially the initial large MMAP attempt by iptables, which was 1.5GB
> > in my case).
>
> Oh wait .... I found a bug a while ago from someone trying to load
> large modules. There is a problem if the kernel grows to need
> additional PTE tables, the top level pointers don't get propagated
> correctly and subsequent access by a thread that didn't actually
> do the allocation would fail. I'm looking into this, including your
> past message about 64-bit PTEs.
additional note:
the problem only shows up for me only when enabling
CONFIG_64BIT_PHYS_ADDR, in case someone had problems reproducing the
issue...
regards,
--
Herbert Valerio Riedel <hvr@hvrlab.org>
next prev parent reply other threads:[~2005-04-28 5:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-26 8:43 iptables/vmalloc issues on alchemy Herbert Valerio Riedel
2005-04-27 18:49 ` Josh Green
2005-04-27 19:06 ` Dan Malek
2005-04-28 5:06 ` Herbert Valerio Riedel [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-28 20:11 Christian Gan
2005-04-28 20:11 ` Christian Gan
2005-04-28 20:56 ` Dan Malek
2005-04-28 20:56 ` Dan Malek
2005-04-28 21:22 Christian Gan
2005-04-28 21:22 ` Christian Gan
2005-04-28 22:16 ` Dan Malek
2005-04-28 22:16 ` Dan Malek
2005-04-28 23:52 ` Thiemo Seufer
2005-04-28 23:16 Christian Gan
2005-04-28 23:16 ` Christian Gan
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=1114664812.4647.6.camel@mini.intra \
--to=hvr@hvrlab.org \
--cc=dan@embeddededge.com \
--cc=jgreen@users.sourceforge.net \
--cc=linux-mips@linux-mips.org \
--cc=ppopov@embeddedalley.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.