Linux filesystem development
 help / color / mirror / Atom feed
From: Pat LaVarre <p.lavarre@ieee.org>
To: linux-fsdevel@vger.kernel.org
Subject: fs oops debuggable in 2.6 with one one machine
Date: 22 Oct 2003 06:44:56 -0600	[thread overview]
Message-ID: <1066826696.7159.70.camel@patehci2> (raw)

Anybody yet work out in detail how to debug oops in filesystems without
connecting a second machine?

I haven't yet made the "more zeroes read back than appended" oops of
udf.ko reliably repeatable, but presuming eventually I do, then my next
hope is to capture the dmesg leading up to the oops.

I followed the web trail:

http://marc.theaimsgroup.com/?l=kernelnewbies&b=200310
http://marc.theaimsgroup.com/?l=kernelnewbies&m=106680564215479
http://kniggit.net/wwol26.html

I found:

---

Virtualizing Linux

One of the most interesting new features in Linux 2.6 is its inclusion
of a "user-mode" architecture. This is essentially a port (like to a
different hardware family) of Linux to itself, allowing for a completely
virtualized Linux-on-Linux environment to be run. The new instance of
Linux runs as if it was a normal application. "Inside" the application,
you can configure fake network interfaces, filesystems, and other
devices through special drivers which communicate up to the host copy of
Linux in a secure way. This has proved quite useful, both for
development purposes (profiling, etc.) as well as for security analysis
and honeypots. While most users will never need this kind of support, it
is an incredibly "cool" feature to have running on your box. (Impress
your friends!)

---

Pat LaVarre



             reply	other threads:[~2003-10-22 12:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-22 12:44 Pat LaVarre [this message]
2003-10-23 12:49 ` fs oops debuggable in 2.6 with one one machine Jan Hudec

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=1066826696.7159.70.camel@patehci2 \
    --to=p.lavarre@ieee.org \
    --cc=linux-fsdevel@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