Your message dated Wed, 20 Jan 2010 13:53:07 +0000
with message-id <e1nxazb-0003vi...@ries.debian.org>
and subject line Bug#550898: fixed in user-mode-linux 2.6.26-1um-2+21
has caused the Debian Bug report #550898,
regarding DASD DIAG driver doesn't work for read-only minidisks (s390, s390x
only)
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 ow...@bugs.debian.org
immediately.)
--
550898: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=550898
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6.26-2-s390x
Version: 2.6.26-19
X-Debbugs-CC: debian-s...@lists.debian.org
This bug report applies to the s390 and s390x Linux kernel architectures only.
I am reasonably certain that this is not a Debian-specific bug but
applies to all distributions. Nevertheless, since I am using Debian
I will report it to Debian. Please call this bug report to the
attention of the appropriate upstream kernel development team.
When using the DASD DIAG driver with a read-only minidisk, the
initialize function of DIAG X'250' fails. The error message produced
goes something like this:
dasd(diag) 0.0.0404: DIAG initialization failed (rc=4)
dasd_generic couldn't online device 0.0.0404 with discipline DIAG rc=-5
Consulting the IBM manual "CP Programming Services" for DIAG X'250',
I find the following explanation for return code 4 for the initialize
function:
Initialization for DIAGNOSE code X'250'
to the specified virtual device is
complete. The virtual device is
read-only. The starting block number and
the ending block number have been stored
in the BIOPL.
In other words, this is a normal condition, not an error. It is
simply a warning that this minidisk is read-only. The correct
response by the program should be to treat a return code of 4
the same as a return code of 0, provided that the device really
is read-only. A return code of 4 for a device that is supposedly
read-write is a sanity-check error that you might want to check
for. Otherwise, a return code of 4 is a normal and expected
condition.
I don't claim to be a C programmer, but it appears to me that
the mdsk_init_io internal subroutine of /drivers/s390/block/dasd_diag.c
is the culprit.
--- End Message ---
--- Begin Message ---
Source: user-mode-linux
Source-Version: 2.6.26-1um-2+21
We believe that the bug you reported is fixed in the latest version of
user-mode-linux, which is due to be installed in the Debian FTP archive:
user-mode-linux_2.6.26-1um-2+21.diff.gz
to main/u/user-mode-linux/user-mode-linux_2.6.26-1um-2+21.diff.gz
user-mode-linux_2.6.26-1um-2+21.dsc
to main/u/user-mode-linux/user-mode-linux_2.6.26-1um-2+21.dsc
user-mode-linux_2.6.26-1um-2+21_i386.deb
to main/u/user-mode-linux/user-mode-linux_2.6.26-1um-2+21_i386.deb
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 550...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
dann frazier <da...@debian.org> (supplier of updated user-mode-linux 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 ftpmas...@debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Tue, 19 Jan 2010 18:32:16 -0700
Source: user-mode-linux
Binary: user-mode-linux
Architecture: source i386
Version: 2.6.26-1um-2+21
Distribution: stable
Urgency: high
Maintainer: User Mode Linux Maintainers <pkg-uml-p...@lists.alioth.debian.org>
Changed-By: dann frazier <da...@debian.org>
Description:
user-mode-linux - User-mode Linux (kernel)
Closes: 332942 444043 513050 522922 550898 552465 558426 559064
Changes:
user-mode-linux (2.6.26-1um-2+21) stable; urgency=high
.
* Rebuild against linux-source-2.6.26 (2.6.26-21):
[ Ben Hutchings ]
* Fix false soft lockup reports for the nohz idle loop
* nohz: Fix two bugs that can keep a processor idle and lead to a
system hang (may fix #496917, #538158 and others)
* usbmidi: Fix crash when device is disconnected (Closes: #513050)
* r8169: Apply various upstream bug fixes
* r8169: Add support for RTL8101e (v2), RTL8102e (v1,v2,v3),
RTL8168c/8111c (v3,v4), RTL8168cp/8111cp (v2,v3), RTL8168d (v1)
(Closes: #552465; may fix #516187)
* Revert patch to sanitise <linux/socket.h>, which introduced
different build failures
* usbnet: Set link down initially for drivers that update link state
(Closes: #444043)
* atl1e: Remove broken implementation of TSO for TCP/IPv6
(Closes: #558426) and allow other hardware offloads to be disabled in
case they are also buggy
.
[ dann frazier ]
* floppy: request and release only the ports we actually use
(Closes: #332942)
* igb: Add 82576 MAC support (Closes: #522922), backport
by Ben Hutchings
* [SCSI] gdth: Prevent negative offsets in ioctl (CVE-2009-3080)
* NFSv4: Fix a problem whereby a buggy server can oops the kernel
(CVE-2009-3726)
* [SCSI] megaraid_sas: remove sysfs dbg_lvl world writeable permissions
(CVE-2009-3889)
* isdn: hfc_usb: Fix read buffer overflow (CVE-2009-4005)
* fuse: prevent fuse_put_request on invalid pointer (CVE-2009-4021)
* hpilo: new PCI ID (Closes: #559064)
* Avoid /proc/$pid/maps visibility during initial setuid ELF loading
(CVE-2009-2691)
* hfs: fix a potential buffer overflow (CVE-2009-4020)
* KVM: x86 emulator: limit instructions to 15 bytes (CVE-2009-4031)
* firewire: ohci: handle receive packets with a data length of zero
(CVE-2009-4138)
* ext4: Avoid null pointer dereference when decoding EROFS w/o a journal
(CVE-2009-4308)
* s390: dasd diag - add support for read-only minidisks (Closes: #550898)
Checksums-Sha1:
ad9733dc7c4cd8fdff5904c8f1961d52db3977ed 1243
user-mode-linux_2.6.26-1um-2+21.dsc
7ac14a7b6bb60654cb8c9595b75632a115bb4758 16601
user-mode-linux_2.6.26-1um-2+21.diff.gz
6bc0fca4ea3760d9b3612801856050adf74a0a2c 5361360
user-mode-linux_2.6.26-1um-2+21_i386.deb
Checksums-Sha256:
3c1b24b7e98b96388cc8286d2056cef9a05079e340dfa079ea2dba8cfc42cc1e 1243
user-mode-linux_2.6.26-1um-2+21.dsc
2fe9ce7d52a67a16bcb3a2c55988e4e4e7563d5f2c5db54d457060fbce813d3a 16601
user-mode-linux_2.6.26-1um-2+21.diff.gz
7133e262a90829a6545b5fb5bb9d4cdac5f6c2f9d80319d782288c967c655275 5361360
user-mode-linux_2.6.26-1um-2+21_i386.deb
Files:
d986558a5d4929a2134d3fab8fcf73df 1243 misc extra
user-mode-linux_2.6.26-1um-2+21.dsc
3e654c18d23bc4bb3691b755d9ad45b0 16601 misc extra
user-mode-linux_2.6.26-1um-2+21.diff.gz
d08d51158ebf10e4fe55806ddee50cb8 5361360 misc extra
user-mode-linux_2.6.26-1um-2+21_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iD8DBQFLVmYZhuANDBmkLRkRAj/YAKCOa3bHPPEJ1vRltHg/9EJutiyXyACdFnj4
lVFuVqQHFe1gqZMycEr/wWg=
=I7b2
-----END PGP SIGNATURE-----
--- End Message ---