From: Nick Piggin <piggin@cyberone.com.au>
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 15:09:49 +1100 [thread overview]
Message-ID: <3FFA350D.2070507@cyberone.com.au> (raw)
In-Reply-To: <3FFA30FA.1040602@conet.cz>
Libor Vanek wrote:
> Hi,
> I'm trying to do some debugging with 2.6.0 + mm1 patch (I attach my
> .config) and I found out this very strange thing when changing
> fs/open.c (about the line 933):
>
> ORIGINAL CODE:
> ...
> asmlinkage long sys_open(const char __user * filename, int flags, int
> mode)
> {
> char * tmp;
> int fd, error;
>
> #if BITS_PER_LONG != 32
> flags |= O_LARGEFILE;
> #endif
> tmp = getname(filename);
> fd = PTR_ERR(tmp);
> ...
>
>
> MY TINY MODIFICATION:
> ...
> 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];
>
>
> #if BITS_PER_LONG != 32
> flags |= O_LARGEFILE;
> #endif
> tmp = getname(filename);
> printk (KERN_INFO "sys_open: %s\n",tmp);
> fd = PTR_ERR(tmp);
> ...
>
>
> This causes kernel to panic during boot. Messages are: (maybe some
> typos - writing from paper)
> ...
> NET: Registering protocol family 17
> Unable to handle kernel paging request at virtual address fffffff2
getname can return errors, actually. Looks like you're trying to print
the string at address -EFAULT.
When in doubt, always suspect your code.
next prev parent reply other threads:[~2004-01-06 4:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-06 3:52 2.6.0-mm1 - kernel panic (VFS bug?) Libor Vanek
2004-01-06 4:09 ` Nick Piggin [this message]
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
[not found] <1aQy3-2y1-7@gated-at.bofh.it>
2004-01-06 5:49 ` Andi Kleen
2004-01-06 12:35 ` Libor Vanek
2004-01-06 12:39 ` Andi Kleen
2004-01-06 12:43 ` Libor Vanek
2004-01-06 13:19 ` Muli Ben-Yehuda
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=3FFA350D.2070507@cyberone.com.au \
--to=piggin@cyberone.com.au \
--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