linux-um archives
 help / color / mirror / Atom feed
From: Blaisorblade <blaisorblade@yahoo.it>
To: Andrew Morton <akpm@osdl.org>
Cc: Jeff Dike <jdike@addtoit.com>,
	user-mode-linux-devel@lists.sourceforge.net,
	LKML <linux-kernel@vger.kernel.org>
Subject: [uml-devel] Uml showstopper bugs for 2.6.14
Date: Tue, 27 Sep 2005 18:46:50 +0200	[thread overview]
Message-ID: <200509271846.51804.blaisorblade@yahoo.it> (raw)

Here's a short list of showstoppers for 2.6.14 release, from the UML point of 
view.

I and/or Jeff know about them, and Jeff might add some other ones. Also UML 
users are welcome (please in this case, especially if you aren't sure if 
you're experiencing a bug or a setup problem, don't CC directly Andrew 
Morton, but instead give me and Jeff a chance to act as a filter).

I hope so to avoid the situation of 2.6.10 release, when a bunch of important 
fixes was in -mm, targeted at 2.6.10, but was merged *after* 2.6.10. That has 
not happened any more, but 2.6.14 has a shorter release cycle, so I'm 
worried.

I initially read 2.6.14 ETA's was around October 7, when is it now?

However, here we go with the showstoppers (mostly regression):

1) I broke SKAS3 with the last merge. The fix is trivial, I just want to 
stress-test it a bit more this time (and run the original LTP failing test 
case, i.e. copy_from_user(dest, (void*) -1, n)).

2) problems with UBD (i.e. _the_ uml block driver): this is pretty dangerous 
and untrivial to fix, even if the code exists.

DESCRIPTION:
with the UBD rewrite to use AIO merged before 2.6.14-rc1, the UBD driver does 
GFP_KERNEL allocations under spinlocks and can have a deadlock (there's an 
host IPC pipe, whose buffer can get filled causing the kernel to sleep). Jeff 
Dike has the fixes for this, but they're not trivial, so he's working on 
them. I think he could send them to Jens Axboe, when he feels them ready. 
Agreed, Jeff?

3) I've a problem with KBUILD_OUTPUT, just fixed, recently introduced. Going 
to properly test the fix and submit it.

4) Not a regression:
I have a bunch of fixes for HPPFS, which went under a review from Al Viro. I'm 
incorporating his suggestions, but the patches are invasive, so probably it's 
better to defer them to 2.6.15. I'm not sure, though.

Jeff, have you any further notes to add?
-- 
Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!".
Paolo Giarrusso, aka Blaisorblade (Skype ID "PaoloGiarrusso", ICQ 215621894)
http://www.user-mode-linux.org/~blaisorblade


	

	
		
___________________________________ 
Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB 
http://mail.yahoo.it



-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

             reply	other threads:[~2005-09-27 17:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-27 16:46 Blaisorblade [this message]
2005-09-27 19:30 ` [uml-devel] Re: Uml showstopper bugs for 2.6.14 Jeff Dike
2005-09-28 12:15   ` Blaisorblade
2005-09-28 14:52     ` Jeff Dike
2005-09-28 16:40       ` Blaisorblade

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=200509271846.51804.blaisorblade@yahoo.it \
    --to=blaisorblade@yahoo.it \
    --cc=akpm@osdl.org \
    --cc=jdike@addtoit.com \
    --cc=linux-kernel@vger.kernel.org \
    --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