Your message dated Fri, 28 Jan 2011 13:32:11 +0000
with message-id <[email protected]>
and subject line Bug#611187: fixed in nbd 1:2.9.16-8
has caused the Debian Bug report #611187,
regarding nbd-server dies due to EFAULT from read
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
611187: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611187
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: nbd-server
Version: 1:2.9.11-3
In an automatic test system (used by xen upstream) I encountered this
failure:
Jan 25 16:12:36 leaf-beetle nbd_server[20034]: Read failed: Bad address
Jan 25 16:12:36 leaf-beetle nbd_server[20033]: Child exited with 1
The client naturally then saw a series of IO failures and was
generally very unhappy.
The problem is not easily reproducible. I have seen similar failures
before but they are very infrequent.
The configuration in this case was:
* Two NBDs: each one of an LVM volume on the server imported by the client
* Each LVM VG backed by a single PV on a physical disk partition
* Both hosts' hardware: rackservers.com AMD-based server
* Both hosts' userland: amd64 lenny userland
* Both hosts' kernel: Xen-enabled xen.org kernel derived from 2.6.32.27
* Both hosts' hypervisor: xen-unstable 4.1.0 RC2+
* nbd server hostname: leaf-beetle
* nbd client hostname: potato-beetle
Full logs can be found here for the next few weeks:
http://www.chiark.greenend.org.uk/~xensrcts/logs/5238/test-amd64-amd64-pair/info.html
I appreciate that this isn't very much to go on. If you would like to
suggest some additional instrumentation, or additional logs to
capture, I will be happy to add that to my test machinery and then
report the results as and when the bug recurs.
Thanks,
Ian.
Here is a copy of the /etc/nbd-server/config from the server:
# generated by ./ts-guests-nbd-mirror
[generic]
user = root
[export0]
exportname = /dev/leaf-beetle.cam.xci-test.com/debian.guest.osstest-disk
port = 4000
[export1]
exportname = /dev/leaf-beetle.cam.xci-test.com/debian.guest.osstest-swap
port = 4001
--- End Message ---
--- Begin Message ---
Source: nbd
Source-Version: 1:2.9.16-8
We believe that the bug you reported is fixed in the latest version of
nbd, which is due to be installed in the Debian FTP archive:
nbd-client-udeb_2.9.16-8_amd64.udeb
to main/n/nbd/nbd-client-udeb_2.9.16-8_amd64.udeb
nbd-client_2.9.16-8_amd64.deb
to main/n/nbd/nbd-client_2.9.16-8_amd64.deb
nbd-server_2.9.16-8_amd64.deb
to main/n/nbd/nbd-server_2.9.16-8_amd64.deb
nbd_2.9.16-8.diff.gz
to main/n/nbd/nbd_2.9.16-8.diff.gz
nbd_2.9.16-8.dsc
to main/n/nbd/nbd_2.9.16-8.dsc
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Wouter Verhelst <[email protected]> (supplier of updated nbd package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Fri, 28 Jan 2011 14:06:48 +0100
Source: nbd
Binary: nbd-server nbd-client nbd-client-udeb
Architecture: source amd64
Version: 1:2.9.16-8
Distribution: unstable
Urgency: high
Maintainer: Wouter Verhelst <[email protected]>
Changed-By: Wouter Verhelst <[email protected]>
Description:
nbd-client - Network Block Device protocol - client
nbd-client-udeb - Network Block Device protocol - client for Debian Installer
(udeb)
nbd-server - Network Block Device protocol - server
Closes: 611187
Changes:
nbd (1:2.9.16-8) unstable; urgency=high
.
* Cherry-pick 3ef52043861ab16352d49af89e048ba6339d6df8 from git HEAD
to fix oversized requests again. This Closes: #611187, which is a
re-introduction of CVE-2005-3534, hence urgency=high
Checksums-Sha1:
7ef445c4e29aea243f657c98b7b6c7983e8404d1 1771 nbd_2.9.16-8.dsc
07fbf38bf5bede1d72f0aab95b0961e9f0fc0a13 84557 nbd_2.9.16-8.diff.gz
2283e8923c9868341b73ae43a526911a57eee292 60448 nbd-server_2.9.16-8_amd64.deb
f1ee5b58c7b90140bf2724d385c75ecd8f5f5568 50858 nbd-client_2.9.16-8_amd64.deb
135d5251f4c21389fe27df1f34581b092bb4d34d 6950
nbd-client-udeb_2.9.16-8_amd64.udeb
Checksums-Sha256:
88597bf9ce3b722a4b7d72899bb9c89453dff0608411ec4be426a66fd025a31b 1771
nbd_2.9.16-8.dsc
0a9053ba4ac4bf6e9a49279b93317f24431f7df9ee1329ea1a958791d4488050 84557
nbd_2.9.16-8.diff.gz
46a1a160bfb29ee37af7262b81c72edaa72549a20cdd1441d6413d6a7613e069 60448
nbd-server_2.9.16-8_amd64.deb
cba562dd67877795faf03883a7b03698731ae930e86f2be6c54700f22c85fd81 50858
nbd-client_2.9.16-8_amd64.deb
501c2cfefe62f721f15d68bc6ea38bbc0d1b43facf37e3de1320a92f06e74003 6950
nbd-client-udeb_2.9.16-8_amd64.udeb
Files:
c4edcb1dc45c72b35778f29a62f1160e 1771 admin optional nbd_2.9.16-8.dsc
edc1a461fabddda47a1f845fd6a6f3b4 84557 admin optional nbd_2.9.16-8.diff.gz
d6bb85404c6effbff4517e0b312784e2 60448 admin optional
nbd-server_2.9.16-8_amd64.deb
fd4244a9c8dfda5faa4e64c95924c347 50858 admin optional
nbd-client_2.9.16-8_amd64.deb
24ca9e6df7f6808c6e6dbecc7694ec35 6950 debian-installer optional
nbd-client-udeb_2.9.16-8_amd64.udeb
Package-Type: udeb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iQIcBAEBAgAGBQJNQsHuAAoJEMKUD5Ub3wqd7WAP+wYUiOPZ6/FqwA6bzV5rCWfi
tA8unwMSmcNIJkikfaj9Cc7FT+CcUJWFKJ9vOnCn9B46TCOYh6tZV1ZVzNdCAlRS
QNIAj/7zqPwpi7fJTg1XNTKPiYFNmxwn1C/xl0Va6MjcqpWYKJa3GbUJ8K6IkdI/
tUdhGUQ15YTMxlW40t+6/TdVAKI72kuvi27wQoZ29m5vm56owbgxFSfofj+Xrijz
LNYV6kmFKYZ4quqWCqOWPYifOGB03Czs7TQRtDjawE37gofhVzfFSqqz68Xh5i/d
UCcCF2ci6XLaP/47uLVESzWGvEnQPC07gmNTrb3AFbW69nP1k7wxCGB4ZLPkwsWX
zZMeK1m46eRf+XwU1LIS0pEwfxe59v98LJ1pHO+U0fAmmNuWr410GiQntpyVYMmf
wefZteWLZsaLhpJ9aXaE1zvLEApRiterteWSC0ZrLFIJ1SUPxHZ0WDardc8luyjj
LDEOgNZumxbMjYuzDaLdzaYk1zs1dtgPTlxpi4TtLfKHBX/fCDR3YYs7HqZf2IMy
YPFVVcCx9O4UK0VHDOCuPsMIZDNOj11dxMEBKvhmHDFVA+FFTkUbA4peISTomtrT
06l3WFvKg/nSj6HP4rmwBX/lWoxBvf86nMIiBsPjNsIGuRmM7HQwSwOIOIBVf0Z1
uinLJEY4AoX0VXAeoBgv
=PDhp
-----END PGP SIGNATURE-----
--- End Message ---
