From: Eddy Yuniar <dogmaphobia@gmail.com>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] problem with hostfs in statfs... (2.6.7)
Date: Thu, 8 Jul 2004 09:14:29 +0700 [thread overview]
Message-ID: <16f5f6240407071914138341e3@mail.gmail.com> (raw)
I''ve runnning a problem when invoking df from the shell.... and got
kernel panic...
the problem is in hostfs_statfs when calling do_statfs, parameter
sf->f_spare should be substituted with sf->f_frsize, because there is
a change in struct kstatfs with addition f_frsize that using one of
f_spare array.... so array f_spare now only have size 5....
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next reply other threads:[~2004-07-08 2:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-08 2:14 Eddy Yuniar [this message]
2004-07-08 3:22 ` [uml-devel] problem with hostfs in statfs... (2.6.7) Mulyadi-Santosa
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=16f5f6240407071914138341e3@mail.gmail.com \
--to=dogmaphobia@gmail.com \
--cc=user-mode-linux-devel@lists.sourceforge.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