From: Benjamin LaHaise <bcrl@kvack.org>
To: Lee <linuxtwidler@gmail.com>
Cc: linux-kernel@vger.kernel.org, pageexec@freemail.hu
Subject: Re: 4k stack overflow and stack traces
Date: Wed, 16 Nov 2005 12:33:58 -0500 [thread overview]
Message-ID: <20051116173358.GA982@kvack.org> (raw)
In-Reply-To: <20051115164005.0d7f5baf@localhost>
On Tue, Nov 15, 2005 at 04:40:05PM -0600, Lee wrote:
> see attached for filesystems, devices, current kernel build config
>
> do you advise doing a make checkstack before or after the patch that you speak of making?
Yes please, that will give us all the datapoints from your particular
gcc version, config and modules.
> I also have iptables configured with nat for local connections enabled
>
> i am also using ethernet bridge (intended for apps like pearpc and qemu,
> which i use very infrequently).
Hmmm, does it trigger on any particular network traffic? I'm wondering
if one of the masquerading modules you're using happens to eat just
enough stack when mixed with the bridging configuration.
-ben
prev parent reply other threads:[~2005-11-16 17:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-10 14:35 4k stack overflow and stack traces Lee
2005-11-15 20:28 ` Benjamin LaHaise
2005-11-15 22:40 ` Lee
2005-11-16 17:33 ` Benjamin LaHaise [this message]
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=20051116173358.GA982@kvack.org \
--to=bcrl@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxtwidler@gmail.com \
--cc=pageexec@freemail.hu \
/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