help-kernel-v1.html 25.5 KB
Newer Older
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"
    "http://www.w3.org/TR/REC-html40/loose.dtd">
<html>
<head>
   <meta content="text/html; charset=iso-8859-1" http-equiv="Content-Type">
<title>Help with getting UML V1.0 ready</title>
</head>
<body alink="#FF0000" vlink="#55188A" link="#0000EF" bgcolor="#FFFFFF" text="#000099">
<table border="0">
<tr align="left">
<td valign="top">
<table border="0">

<tr align="left"><td valign="top" >
<img src="http://user-mode-linux.sourceforge.net/uml-small.png" height="171" width="120"/> 
</td></tr>

<tr align="left"><td valign="top" bgcolor="#e0e0e0">
<font size="-1"><a href="http://user-mode-linux.sourceforge.net/index.html">Site Home Page</a></font>
<br>
              <font size="-1"><a href="http://uml.harlowhill.com">The UML Wiki</a></font>
<br>
              <font size="-1"><a href="http://usermodelinux.org">UML Community Site</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/roadmap.html">The UML roadmap</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/uses.html">What it's good for</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/case-studies.html">Case Studies</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/kernel.html">Kernel Capabilities</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/dl-sf.html">Downloading it</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/run.html">Running it</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/compile.html">Compiling</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/install.html">Installation</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/skas.html">Skas Mode</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/patches.html">Incremental Patches</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/tests.html">Test Suite</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/devanon.html">Host memory use</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/fs_making.html">Building filesystems</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/faq.html">Troubles</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/contrib.html">User Contributions</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/links.html">Related Links</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/todo.html">The ToDo list</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/projects.html">Projects</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/diary.html">Diary</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/thanks.html">Thanks</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/contacts.html">Contacts</a></font>
</td></tr>

<tr align="left"><td valign="top" bgcolor="#e0e0e0">Tutorials<br>
<font size="-1"><a href="http://user-mode-linux.sourceforge.net/UserModeLinux-HOWTO.html">The HOWTO (html)</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/UserModeLinux-HOWTO.txt">The HOWTO (text)</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/hostfs.html">Host file access</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/input.html">Device inputs</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/shared_fs.html">Sharing filesystems</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/fs.html">Creating filesystems</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/resize.html">Resizing filesystems</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/networking.html">Virtual Networking</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/mconsole.html">Management Console</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/debugging.html">Kernel Debugging</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/honeypots.html">UML Honeypots</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/gprof.html">gprof and gcov</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/xtut.html">Running X</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/trouble.html">Diagnosing problems</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/config.html">Configuration</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/slack_readme.html">Installing Slackware</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/arch-port.html">Porting UML</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/iomem.html">IO memory emulation</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/2G-2G.html">UML on 2G/2G hosts</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/lksct/index.html">Adding a UML system call</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/nesting.html">Running nested UMLs</a></font>
</td></tr>

<tr align="left"><td valign="top" bgcolor="#e0e0e0">How you can help<br>
<font size="-1"><a href="http://user-mode-linux.sourceforge.net/help-gen.html">Overview</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/help-doc.html">Documentation</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/help-userspace.html">Utilities</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/help-kernel-v1.html">Kernel bugs</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/projects.html">Kernel projects</a></font>
</td></tr>

<tr align="left"><td valign="top" bgcolor="#e0e0e0">Screenshots<br>
<font size="-1"><a href="http://user-mode-linux.sourceforge.net/net.html">A virtual network</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/x.html">An X session</a></font>
</td></tr>

<tr align="left"><td valign="top" bgcolor="#e0e0e0">Transcripts<br>
<font size="-1"><a href="http://user-mode-linux.sourceforge.net/login.html">A login session</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/debug-session.html">A debugging session</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/slackinst.html">Slackware installation</a></font>
</td></tr>

<tr align="left"><td valign="top" bgcolor="#e0e0e0">Reference<br>
<font size="-1"><a href="http://user-mode-linux.sourceforge.net/switches.html">Kernel switches</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/slack_readme.html">Slackware README</a></font>
</td></tr>

<tr align="left"><td valign="top" bgcolor="#e0e0e0">Papers<br>
<font size="-1"><a href="http://user-mode-linux.sourceforge.net/als2000/index.html">ALS 2000 paper (html)</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/als2000.tex">ALS 2000 paper (TeX)</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/slides/als2000/slides.html">ALS 2000 slides</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/slides/lca2001/lca.html">LCA 2001 slides</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/slides/ols2001/index.html">OLS 2001 paper (html)</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/ols2001.tex">OLS 2001 paper (TeX)</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/als2001/index.html">ALS 2001 paper (html)</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/als2001.tex">ALS 2001 paper (TeX)</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/slides/ists2002/umlsec.htm">UML security (html)</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/slides/lca2002/lca2002.htm">LCA 2002 (html)</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/slides/wvu2002/wvu2002.htm">WVU 2002 (html)</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/slides/ists_rt/ists_rt.htm">Security Roundtable (html)</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/slides/ols2002/ols2002.html">OLS 2002 slides</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/slides/lwe2005/LWE2005.html">LWE 2005 slides</a></font>
</td></tr>

<tr align="left"><td valign="top" bgcolor="#e0e0e0">Fun and Games<br>
<font size="-1"><a href="http://user-mode-linux.sourceforge.net/cgi-bin/hangman">Kernel Hangman</a></font>
<br>
              <font size="-1"><a href="http://user-mode-linux.sourceforge.net/sdotm.html">Disaster of the Month</a></font>
</td></tr>

</table>
</td>
<td valign="top" align="left">

This is the current list of things I want to fix before I consider UML
to have reached version 1.
<p>
I've attached a description to each one which will provide some
guidance as to proceed with it.  If you need more details, contact me
or send mail off to the uml-devel list.

<p>
          <ul>
            <li>
              <b>
                <p>
My attempts to run the Debian install procedure hung UML while it was
probing disks.  I never figured out what was happening.
</b>
              <p>
If someone verifies that UML can run a Debian installation, I'll
consider this fixed.
</li>
            <p>
            <li>
              <b>
                <p>
Make UML build without warnings
</b>
              <p>
I've been knocking these off one by one.  The remaining ones are
mostly cries for reorganization.  There are pieces of userspace code
in kernel files which call libc functions without there being
declarations in scope.  Mostly, these things need to be separated from
whatever kernel code they're in, and moved to a userspace file.
<p>
An exception to this is the pair of warnings from kernel/timer.c.  I'm
going to fix this by bumping UML's HZ to 50.
<p>
Remember the errno redefinition warning in user_syms.c during the deb build.
</li>
            <p>
            <li>
              <b>
                <p>
Make sure that each clock tick gets counted
</b>
              <p>
If you run UML under load for a while, you'll notice that clock ticks
are being missed.  You can see this by doing a 'ps uax' every once in
a while, and noticing that process start times are moving.  I made an
attempt to fix this by never having SIGVTALRM or SIGALRM blocked and
doing some fancy flag checking to make sure that the IRQ handler is
only called if it's safe, and otherwise just bumping a count of missed
ticks.  The next time it's safe, the IRQ handler will be called once
for the current tick and once for each previously missed tick,
catching the system up with the real time.
<p>
This doesn't fix it for some reason.  The only reason I can think of
is that the signals are getting stacked because a second one comes in
before the first one has been collected by the handler.  I have a hard
time believing that the host can be so bogged down that it can't call
the signal handler within 1/HZ seconds of the alarm happening.  The
signal is going through the tracing thread courtesy of ptrace, so
maybe that's introducing enough delay to stack the signals.
</li>
            <p>
            <p>
            <li>
              <b>
                <p>
Figure out the hostfs crash that Larent Bonnaud is seeing
</b>
              <p>
Laurent hasn't complained about this recently.  If he doesn't, I'll
just consider this fixed.
</li>
            <p>
            <li>
              <b>
                <p>
make 'gdb=pty' work
</b>
              <p>
Run UML with 'debug gdb=pty' on the command line, attach to whatever
pty gdb gets, and you'll see the problem.  There's some major problem
with the terminal modes that I've never figured out.
</li>
            <p>
            <li>
              <b>
                <p>
protect kernel memory from userspace
</b>
              <p>
Fixing this will make it impossible for a nasty UML user to escape
from UML and execute arbitrary system calls on the host.  It has four
pieces:
<ul>
<li>
Write-protect kernel physical and virtual memory whenever UML is in
userspace.  The exception to this is the process kernel stack, which
needs to be writable in order for a signal handler to be run on it.
This is OK because whatever the process puts there will just be
overwritten by the signal handler.  This is partially implemented -
kernel physical memory is protected, except for the four pages making
up the task structure and stack.  Protecting the task structure is
complicated because there is some UML code which effectively runs in
userspace which calls the process signal handler to deliver signals.
It needs to be able to write to the task structure.  I think this fix
is to move that code to before the signal starts being delivered,
which will involve redoing parts of the signal delivery code.
Protecting kernel virtual memory is a matter of walking the kernel
page tables and write-protecting everything that's mapped there.
</li>
<li>
Locating and disabling all drivers that provide access to kernel
memory through interfaces such as /proc/kcore.
</li>
<li>
Fixing the access_ok macro so it rejects any attempt to fake the
kernel into changing its own memory by passing a kernel address as an
argument to a system call.
</li>
<li>
In the host kernel, adding a new personality which segfaults any
attempt to execute a SysV system call.  These are not traced by
ptrace, so a process that knows how to use them is not jailed inside UML.
</li>
</ul>
</li>
            <p>
            <li>
              <b>
                <p>
Figure out why the io_thread loses its parent and its connection to the kernel
</b>
              <p>
This happened once, a long time ago.  The system hung because the IO
thread lost its connection to UML somehow.  I haven't seen it since,
so this will probably be considered fixed.
</li>
            <p>
            <li>
              <b>
                <p>
Get either Myrtal Meep or Matt Clay 
to confirm (or not) that they can no longer crash UML with 
Apache/Perl/MySQL.  This will probably be fixed with the new network drivers. 
</b>
              <p>
The new network drivers probably fixed these problems.  This will be
considered fixed unless people start complaining about it again.
</li>
            <p>
            <li>
              <b>
                <p>
Disable SIGIO on file descriptors which are already being handled.
This will cut off some interrupt recursion. 
</b>
              <p>
This is an efficiency thing and stack depth precaution.  We don't want
sigio_handler to run recursively on the same descriptor because the
descriptor will be handled at the top level.
</li>
            <p>
            <li>
              <b>
                <p>
Figure out why gdb can't use fd chan (blinky@gmx.net)
</b>
              <p>
One of the ioctls that sets up the terminal for gdb returns EPERM.
</li>
            <p>
            <li>
              <b>
                <p>
Figure out why repeated 'tail /dev/zero' with swap causes process segfaults
</b>
              <p>
I stopped being able to reproduce this, so it might be considered
mysteriously fixed at some point.
</li>
            <p>
            <li>
              <b>
                <p>
Set SA_RESTART on SIGPROF
</b>
              <p>
This will prevent SIGPROF from causing system calls on the host from
returning EINTR and messing things up inside UML.
</li>
            <p>
            <li>
              <b>
                <p>
Allow registration of sockets for panics and console output
</b>
              <p>
This involves some work on the mconsole client side to support making
the requests and work in UML to add the mconsole notification to the
panic_notify_chain and to somehow get console output to the client.
My best idea on doing this is to add support for multiple channels on
consoles and support for write-only channels.  Then the mconsole
client can stack a write-only channel to a socket or something on top
of whatever channel is already there.
</li>
            <p>
            <li>
              <b>
                <p>
Replace dentry_name with d_name
</b>
              <p>
Cleanup - I implemented dentry_name, not knowing about d_name, which
does the same thing.  One problem might be that dentry_name expects
the file to exist, which might cause something to break when d_name
returns a '/foo/bar/baz (deleted)' name.
</li>
            <p>
            <li>
              <b>
                <p>
Bind a UML unix socket to a host unix socket
</b>
              <p>
This is a cute feature which would involve passing something like
'hostsock=/tmp/.X11-unix/X0,X' on the command line, which would cause
the hostsock driver to create a /proc/hostsock/X unix socket inside
UML and pass all operations and data on it through to the host's
/tmp/.X11-unix/X0.  Then, you'd create /tmp/.X11-unix/X0 in UML as a
link to /proc/hostsock/X and be able to run X clients on the host X
server without needing the network up.
</li>
            <p>
            <li>
              <b>
                <p>
Dynamically allocate all driver descriptors
</b>
              <p>
The static arrays in the drivers should go away and be replaced by
dynamically allocated buffers, maybe in a list.  This will turn
lookups of particular devices into O(N) operations, but maybe that's
OK.  Also, the transport arrays in the various transports should
similarly go away.
</li>
            <p>
            <li>
              <b>
                <p>
Make slip_tramp conditional in slip_close
</b>
              <p>
slip_open doesn't always invoke the helper through slip_tramp, so
slip_close similarly shouldn't.
<p>
The real problem here is that when a gateway address isn't specified for
slip, it just doesn't work at all.
</li>
            <p>
            <li>
              <b>
                <p>
many du / causes slab cache corruption
</b>
              <p>
This wasn't entirely reproducable, but I did see a couple cases of
panics with slab corruption when running a lot of du's.  I fixed the
process segfault problem, and this problem has probably disappeared as
well.
</li>
            <p>
            <li>
              <b>
                <p>
Adding an eth device via the mconsole (and probably the command line)
won't necessarily configure the device that was named
</b>
              <p>
The kernel does its own ordering of devices, so configuring eth1 without
configuring eth0 gives you eth0.
</li>
            <p>
            <li>
              <b>
                <p>Implement /proc/umid
</b>
              <p>
This would let UML be configured on the inside with knowledge of what
instance it is.
</li>
            <p>
            <li>
              <b>
                <p>
Fix the ubd rounding bug spotted by Steve Schmidtke and Roman Zippel.
</b>
              <p>
If the number of sectors isn't a multiple of 8, then the bitmap will
be a a byte shorter than it should be. 
</li>
            <p>
            <li>
              <b>
                <p>
gdb should be the last thing to be shut down so that breakpoints can
be set late in the shutdown process.
</b>
              <p>
</li>
            <p>
            <li>
              <b>
                <p>
Have the __uml_exitcall handlers check to see if they need to do anything.
</b>
              <p>
If UML is ^C-ed before things are set up, then the cleanup handlers are
cleaning up after things which were never initialized.
</li>
            <p>
            <li>
              <b>
                <p>
Find the race that causes the kernel to run before the debugger is running,
and which then causes a panic and segfault.
</b>
              <p>
</li>
            <p>
            <li>
              <b>
                <p>
Tests that need writing
<ul>
<li>
Build and load some modules to check for unexported symbols
</li>
<li>
Swap testing - qsbench, low-memory kernel build
</li>
<li>
Rerun some existing tests through hostfs
</li>
</ul>
</b>
              <p>
</li>
            <p>
            <li>
              <b>
                <p>
Figure out why gdb inside UML sometimes misses breakpoints.
</b>
              <p>
</li>
            <p>
            <li>
              <b>
                <p>
^C doesn't work well in a busy loop in __initcall code.  I've seen the
process die with a SIGINT as well as have the SIGINT arrive to a
sleeping process, panicing the tracing thread.
</b>
              <p>
</li>
            <p>
            <li>
              <b>
                <p>
When setting a conditional breakpoint on __free_pages in
free_all_bootmem_core and continuing, UML hangs.
</b>
              <p>
It's not a hang.  The conditional breakpoint is in a long loop, and that
makes it take a while.  ^C to gdb seems to be ignored for some reason.  UML
sees it and passes it right along to gdb, which does nothing about it.
</li>
            <p>
            <li>
              <b>
                <p>
Figure out what to do with __uml_setup in modules.  A lot of these should
end up being normal __setup, since they don't have to happen before the
kernel runs.
</b>
              <p>
</li>
            <p>
            <li>
              <b>
                <p>
Figure out why UML died nastily after ^C-ing it and hitting it in userspace.
</b>
              <p>
</li>
            <p>
            <li>
              <b>
                <p>
Telnetting to a console when in.telnetd is non-executable produces an
error and a crash from a sleeping process segfaulting.
</b>
              <p>
</li>
            <p>
            <li>
              <b>
                <p>
Single-stepping when a signal has arrived doesn't work.  gdb
singlesteps, sees the signal, and single-steps with the signal.  The
signal is handled immediately, stepping the process into the handler.
The original instruction was never executed, so when gdb puts the
breakpoint back and the handler returns, the breakpoint is hit again.
</b>
              <p>
</li>
            <p>
            <li>
              <b>
                <p>
The _to_user routines refer to user data without using copy_to_user.
</b>
              <p>
</li>
            <p>
            <li>
              <b>
                <p>
How to cause a strange userspace segfault - run the new UML inside UML
under gdb.  Put a breakpoint on create_elf_tables.  'finish', 'next', 
segfault.
</b>
              <p>
</li>
            <p>
            <li>
              <b>
                <p>
With an old port-helper hanging on to a port, running a UML which want those
ports causes all of the consoles and serial lines to output their login
prompts to stdout.
</b>
              <p>
</li>
            <p>
            <li>
              <b>
                <p>
Assigning console and serial line devices to files doesn't work cleanly.
</b>
              <p>
UML tries to register the descriptors for SIGIO.  Some other mechanism is
needed for feeding the file data into userspace.
</li>
            <p>
            <li>
              <b>
                <p>
Make sure that irqs are deactivated or freed when their descriptors are
closed.
</b>
              <p>
</li>
            <p>
            <li>
              <b>
                <p>
Things to audit:
<ul>
<li>
Make sure that destructors exactly undo everything the constructor does
</li>
<li>
Set FD_CLOEXEC on any descriptors that don't need to be passed across execs.
</li>
<li>
Make sure any protocols are 64-bit clean - this means not using ints, longs,
etc.  Also, maybe enums are bad.
</li>
</ul>
</b>
              <p>
</li>
            <p>
            <li>
              <b>
                <p>
port_kern.c has port_remove_dev and port_kern_free which do almost the
same things.
</b>
              <p>
</li>
            <p>
            <li>
              <b>
                <p>
Make sure that return values are actually used.
</b>
              <p>
</li>
            <p>
            <li>
              <b>
                <p>
skas4 things - remove the extra two context switches per system call,
make sure it compiles with CONFIG_PROC_MM off, implement the mm
indirector, move PTRACE_LDT to /dev/mm, fix PTRACE_FAULTINFO to return
trap type and err, allow the environment, argument, etc pointers of an
mm to be set.
</b>
              <p>
</li>
            <p>
          </ul>


</td>
</tr>
</table>

<center>
<font size="-1">Hosted at </font>
    <a href="http://sourceforge.net">
    <img src="http://sourceforge.net/sflogo.php?group_id=429" width="88" height="31" border="0" alt="SourceForge Logo">
    </a>
</center>
</body>
</html>