From: Jeff Dike <jdike@addtoit.com>
To: Gerd Stolpmann <info@gerd-stolpmann.de>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Integer overflows in new AIO ubd driver
Date: Mon, 27 Mar 2006 10:38:32 -0500 [thread overview]
Message-ID: <20060327153832.GB3666@ccure.user-mode-linux.org> (raw)
In-Reply-To: <1143398965.11224.146.camel@localhost.localdomain>
On Sun, Mar 26, 2006 at 08:49:25PM +0200, Gerd Stolpmann wrote:
> I recently tried to benchmark the new AIO-based ubd driver (including
> O_DIRECT), and ran into serious problems with filesystems > 4GB. I think
> I found the problem; two overflows in ubd_kern.c (see patch).
The first bit looks reasonable. I would change start to an unsigned
long long instead of casting, though.
> I also experienced (hard) lockups when doing lots of I/O. But this seems
> to be unrelated to this problem (but who knows).
What was your workload?
Jeff
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2006-03-27 15:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-26 18:49 [uml-devel] Integer overflows in new AIO ubd driver Gerd Stolpmann
2006-03-27 15:38 ` Jeff Dike [this message]
2006-03-27 15:47 ` Gerd Stolpmann
2006-03-29 19:33 ` Jeff Dike
2006-03-29 21:16 ` Gerd Stolpmann
2006-03-30 18:49 ` Jeff Dike
2006-05-08 17:26 ` Jeff Dike
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=20060327153832.GB3666@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=info@gerd-stolpmann.de \
--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