From: Andi Kleen <ak@muc.de>
To: Libor Vanek <libor@conet.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-mm1 - kernel panic (VFS bug?)
Date: Tue, 06 Jan 2004 06:49:16 +0100 [thread overview]
Message-ID: <m3znd139ur.fsf@averell.firstfloor.org> (raw)
In-Reply-To: <1aQy3-2y1-7@gated-at.bofh.it> (Libor Vanek's message of "Tue, 06 Jan 2004 05:00:15 +0100")
Libor Vanek <libor@conet.cz> writes:
> ...
> asmlinkage long sys_open(const char __user * filename, int flags, int mode)
> {
> char * tmp;
> int fd, error;
> char tmp_path[PATH_MAX],tmp2_path[PATH_MAX];
PATH_MAX is 4096. The i386 stack is only 6k. You already overflowed it.
You're lucky if your machine only panics, much worse things can happen
with kernel stack overflows.
-Andi
next parent reply other threads:[~2004-01-06 5:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1aQy3-2y1-7@gated-at.bofh.it>
2004-01-06 5:49 ` Andi Kleen [this message]
2004-01-06 12:35 ` 2.6.0-mm1 - kernel panic (VFS bug?) Libor Vanek
2004-01-06 12:39 ` Andi Kleen
2004-01-06 12:43 ` Libor Vanek
2004-01-06 13:19 ` Muli Ben-Yehuda
2004-01-06 3:52 Libor Vanek
2004-01-06 4:09 ` Nick Piggin
2004-01-06 4:12 ` Valdis.Kletnieks
2004-01-06 4:24 ` Libor Vanek
2004-01-06 4:35 ` Valdis.Kletnieks
2004-01-06 4:30 ` viro
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=m3znd139ur.fsf@averell.firstfloor.org \
--to=ak@muc.de \
--cc=libor@conet.cz \
--cc=linux-kernel@vger.kernel.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