Your message dated Sun, 13 Mar 2016 19:47:11 +0000 with message-id <[email protected]> and subject line Bug#813995: fixed in flash-kernel 3.35+deb8u3 has caused the Debian Bug report #813995, regarding flashcp writes to nand without being aware of bad blocks 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.) -- 813995: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813995 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: flash-kernel Version: 3.35+deb8u2 Severity: critical Justification: causes serious data loss Control: block 806926 with -1 Hello, when flash-kernel writes a kernel/initrd to NAND flash it uses plain write(2) to /dev/mtdX (flash-kernel < 3.52) or flashcp (flash-kernel >= 3.52). If the device being written to has bad blocks these are tried to be erased and written by both approaches. This results in a non-booting system at best. In general writing to bad blocks can also affect other (otherwise good) blocks and so result in loss of unrelated data. I never saw this in practise, but the manufacturers of NAND flash say so. I didn't check which machines are affected, but Netgear ReadyNAS 102/104 (which isn't in flash-kernel's database yet, but see below for the obvious entry to add support for them and #806926) is affected and flash kernel managed to break a ReadyNAS 102 already (non-permanently by good fortune as far as I can tell up to now). I guess there are several other machines affected though. The right fix is to use nandwrite to write to NAND flash and only use flashcp for NOR. Something like test -f /sys/class/mtd/mtdX/oobsize could be used to detect if the device is NAND or NOR. But there might be more reliable ways I'm not aware of. I will debug/test a bit more with the broken rn102 (and its owner :-) to maybe come up with a patch, but if someone beats me that's very welcome, too. Best regards Uwe -- System Information: Debian Release: 8.2 APT prefers stable APT policy: (990, 'stable'), (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: armhf (armv7l) Kernel: Linux 3.16.0-4-armmp (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages flash-kernel depends on: ii debconf [debconf-2.0] 1.5.56 ii devio 1.2-1 ii initramfs-tools 0.120 ii linux-base 3.5 ii ucf 3.0030 Versions of packages flash-kernel recommends: ii u-boot-tools 2014.10+dfsg1-5 flash-kernel suggests no packages. -- Configuration Files: /etc/flash-kernel/db changed: Machine: NETGEAR ReadyNAS 104 DTB-Id: armada-370-netgear-rn104.dtb DTB-Append: yes Mtd-Kernel: uImage Mtd-Initrd: minirootfs U-Boot-Kernel-Address: 0x04000000 U-Boot-Initrd-Address: 0x05000000 Required-Packages: u-boot-tools -- debconf information: flash-kernel/linux_cmdline: quiet
--- End Message ---
--- Begin Message ---Source: flash-kernel Source-Version: 3.35+deb8u3 We believe that the bug you reported is fixed in the latest version of flash-kernel, which is due to be installed in the Debian FTP archive. 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. Uwe Kleine-König <[email protected]> (supplier of updated flash-kernel 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: SHA512 Format: 1.8 Date: Thu, 10 Mar 2016 20:30:19 +0100 Source: flash-kernel Binary: flash-kernel flash-kernel-installer Architecture: source Version: 3.35+deb8u3 Distribution: stable Urgency: medium Maintainer: Debian Install System Team <[email protected]> Changed-By: Uwe Kleine-König <[email protected]> Description: flash-kernel - utility to make certain embedded devices bootable flash-kernel-installer - Make the system bootable (udeb) Closes: 794265 813995 Changes: flash-kernel (3.35+deb8u3) stable; urgency=medium . [ Karsten Merker ] * Disable the use of modprobe and udevadm in the mtdblock() function while running the testsuite. . [ Ian Campbell ] * Use /dev/mtdN when flashing, rather than needlessly going through the mtdblock layer (which is problematic on some platforms/kernels). (Closes: #794265) . [ Uwe Kleine-König ] * use nandwrite when writing to nand flash. (Closes: #813995) Checksums-Sha1: 9513e75b4356dd139b83bd2803e9a38e9333db13 1521 flash-kernel_3.35+deb8u3.dsc 8e3fd25cac663e1970160592288d6369a59d2d17 57300 flash-kernel_3.35+deb8u3.tar.xz Checksums-Sha256: 7709407aca324aac211d9253a7a07e8ac100e6348e6068fc32cfd5068a18b016 1521 flash-kernel_3.35+deb8u3.dsc f3dc8e240a6b98c15013f64e0d7ef17b5fb4a1a729f085890debabeeaa1197d4 57300 flash-kernel_3.35+deb8u3.tar.xz Files: 22ec45ca580314816eae50f0d0ca70b3 1521 utils optional flash-kernel_3.35+deb8u3.dsc 4bef47671a27faa3a65a46edfd40a537 57300 utils optional flash-kernel_3.35+deb8u3.tar.xz -----BEGIN PGP SIGNATURE----- iQEcBAEBCgAGBQJW5HtbAAoJEMH8FHityuwJdHMH/2NSrfdsdithVLt3fe5x4J6F bH0hPeMUTghYUp6JgiUPXUfwywM9ggnB/Rx7JgAcRQhaXoXLdAY5LtQ1hT3g2Wue A6EnQAL15PUxrrkBq3KnJhavL/g+Z06K4fLSQ0bJ4U8qJDD7J0Q0ZAkyorSPvJue pIoFWeP3o2LMgrngQcPmj6/z/RCG+R31tqLTQtFhVMr09Er8+wpPORedJaCOTor2 8aPd3jAqze7ZPWrGcYuHwnAvDcLxXgNoUWsdLFavC2bBpLsc7jBz4mJFiL/rSOoP Us/RuTxDSLp0DnFhziwNLYNmFaef9Ra3gd/BD5AL/+l4NR6a5RDYELgbw1QLemQ= =m28c -----END PGP SIGNATURE-----
--- End Message ---
