From: Blaisorblade <blaisorblade@yahoo.it>
To: luothing@sina.com
Cc: user-mode-linux-devel@lists.sourceforge.net,
Jeff Dike <jdike@addtoit.com>
Subject: [uml-devel] Re: RE:Fixed - copy_from_user(dest, -1,...) hangs in TT mode (was: Re: [um
Date: Tue, 20 Sep 2005 20:25:13 +0200 [thread overview]
Message-ID: <200509202025.15447.blaisorblade@yahoo.it> (raw)
In-Reply-To: <20050920070918.92204.qmail@mail35-142.sinamail.sina.com.cn>
On Tuesday 20 September 2005 09:09, luothing@sina.com wrote:
> <pre>Hi:
> I simply apply the patch, and run new round ltp on TT mode, and found
> most part of problem is disappear, that\'s a real good news.
> the failure list is:
> fcntl23
As I specified in a separate mail, that's a host bug too, due to having the
file already open for writing. Are you a LTP developer like I guessed or I
understood something wrong?
From the man page:
F_WRLCK
Take out a write lease. This will cause us to be
notified when another process opens the
file (for reading or writing) or truncates it. A write
lease may be placed on a file
only if no other process currently has the file open.
In the current Linux implementation, that becomes "no process, including the
caller, has the file open for writing".
So fixing the test-case to open the file for reading only, or closing and
reopening (if O_CREAT is a problem), would make it pass. Not sure it's right,
but there's no standard for leases IIRC (I'm not at all an expert about this
though, so correct me please).
> ioperm* iopl*
Granted
> nanosleep02 it seems time is not precise
Yes, we'll look at it.
> setregid02 with note \"setregid(65535, -1) failed (1) but did
> not set the expected errno (22).\"
Fails on the host too (same Linux version).
> > Patches are attached against 2.6.13 - apply uml-fault-micro-cleanups
> > before the rest. They\'ll be all included in 2.6.13-bs1. Btw, what\'s
> > your name? I\'d like to credit you in the changelog.
> you can call me: LuoXin
> > I also fixed the modify_ldt01 problem (trivial missing break;), and
> > modify_ldt02 doesn\'t create host problems here (but it\'s an older
> > release) -
> It maybe relate to my test environment, I use kernel(linux-2.6.9-prep) from
> redhat, when I apply skas3-v8.2 patch, I need to modify some code, which I
> am not sure, and I test this testcase on office kernel linux-2.6.12.1, it
> passed
> </pre>
--
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
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
parent reply other threads:[~2005-09-20 18:26 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20050920070918.92204.qmail@mail35-142.sinamail.sina.com.cn>]
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=200509202025.15447.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--cc=jdike@addtoit.com \
--cc=luothing@sina.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