Bug#837588: vmlinux in linux-image packages is unstripped
I pushed a fix to the sid branch which I've tested on a powerpc porterbox. Ben. -- Ben Hutchings A free society is one where it is safe to be unpopular. - Adlai Stevenson signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#838607: linux-image-4.7.0-0.bpo.1-amd64-unsigned: new file date writing issue
Processing control commands: > tag -1 unreproducible moreinfo Bug #838607 [linux-image-4.7.0-0.bpo.1-amd64-unsigned] linux-image-4.7.0-0.bpo.1-amd64-unsigned: new file date writing issue Added tag(s) moreinfo and unreproducible. -- 838607: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838607 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#838607: linux-image-4.7.0-0.bpo.1-amd64-unsigned: new file date writing issue
Control: tag -1 unreproducible moreinfo On Thu, 2016-09-22 at 18:43 -0400, westlake wrote: > Package: linux-image-4.7.0-0.bpo.1-amd64-unsigned > Version: 4.7.2-1~bpo8+1 > Severity: normal > > There's a bug with ext4 on the new 4.7 kernel -- rare but it happened > here on an ext4 mountpoint (/home /dev/md1 ext4 rw,relatime,data=ordered) > > when a new file is created, the "create time" is not properly set.(2014 > was written as the create year instead of 2016) Are the month, day and time roughly correct, or also incorrect? Timestamps on ext4 are stored in Unix time format (seconds since 1970) and an offset of 2 years is not a round number of seconds, so there's no obvious way for a bug to result in a shift of exactly 2 years. > it occured today after I updated to 4.7 so I can only assume it has > something to do with it.. Have you checked that the real-time clock is set correctly (hwclock -r)? Ben. > my system here has "mdadm" containers, and perhaps it's possible a set > of conditions allowed this rarity to occur. -- Ben Hutchings A free society is one where it is safe to be unpopular. - Adlai Stevenson signature.asc Description: This is a digitally signed message part
Bug#827618: similar bug w/ linux-image-4.7.0-1-amd64{,-unsigned}
On Thu, 2016-09-22 at 16:28 +0200, Felix C. Stegerman wrote: > Hi, > > This time I replaced linux-image-4.7.0-1-amd64 w/ > linux-image-4.7.0-1-amd64-unsigned. Then I ran: > > $ sudo aptitude purge ~c > ... > Purging configuration files for linux-image-4.7.0-1-amd64 (4.7.2-1+s1) ... > ... > rmdir: failed to remove '/lib/modules/4.7.0-1-amd64': Directory not empty > ... > > Not only did this cause dpkg to fail, it also removed modules.alias > etc. So replacing the signed kernel package with the unsigned one > still causes some problems. I think I misunderstood this bug originally. However it was reported again as #836282 and I think it's really fixed in version 4.7.4-1. Ben. -- Ben Hutchings A free society is one where it is safe to be unpopular. - Adlai Stevenson signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#837588: hppa: Please disable CONFIG_FTRACE for hppa architecture
Processing control commands:
> reopen -1
Bug #837588 {Done: Ben Hutchings } [linux] hppa: Please
disable CONFIG_FTRACE for hppa architecture
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions linux/4.7.4-1.
> retitle -1 vmlinux in linux-image packages is unstripped
Bug #837588 [linux] hppa: Please disable CONFIG_FTRACE for hppa architecture
Changed Bug title to 'vmlinux in linux-image packages is unstripped' from
'hppa: Please disable CONFIG_FTRACE for hppa architecture'.
--
837588: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837588
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#837588: hppa: Please disable CONFIG_FTRACE for hppa architecture
Control: reopen -1 Control: retitle -1 vmlinux in linux-image packages is unstripped On Thu, 2016-09-22 at 21:18 +0200, Helge Deller wrote: > Hi Ben, > > On 19.09.2016 20:56, Ben Hutchings wrote: > > > > On Mon, 2016-09-19 at 20:50 +0200, Helge Deller wrote: > > > > > > On 19.09.2016 19:41, Ben Hutchings wrote: > > > > > > > > On Mon, 2016-09-12 at 20:28 +0100, Ben Hutchings wrote: > > > > > > > > > > On Mon, 2016-09-12 at 18:17 +0200, Helge Deller wrote: > > > > > > > > > > > > > > > > > > So, can you please deactivate CONFIG_FTRACE completely for 32- and > > > > > > 64bit hppa configs? > > > > > > Is it sufficient to add "CONFIG_FTRACE=n" to > > > > > > debian/config/hppa/config ? > > > > > > > > > > Done. > > Argh - this didn't fixed the size issues on hppa. > I was under the wrong assumption, that CONFIG_FTRACE (which was implemented in > kernel 4.7 for the first time) was the culprit which increased the kernel > size. > This assumption was wrong. > > The attached patch finally fixes the issue. > It re-enables the CONFIG_FTRACE option (which is set by your upper config > files), > and disables CONFIG_DEBUG_INFO which was now suddenly enabled by the debian > kernel 4.7 (it wasn't in 4.6!). > I enabled CONFIG_DEBUG_RODATA to write-protect kernel memory as well. > > The main problem was, that the generated dwarf debug info increases the > kernel vmlinux image from 17MB to 97MB in disk size. > I've compile- and run-tested the patch and built a +b1 kernel. > > Can you apply the attached patch on top of current git? > I can commit it myself as well if you like. This is not the correct fix, nor is this an hppa-specific problem. We need to strip debug information out of the kernel image that goes into linux-image-[-unsigned], and currently we don't do that explicitly. Previously we only enabled debug information for x86 and s390, and for those the upstream build rules already strip debug information before compressing the kernel. Here's the current status, so far as I can see: alpha: vmlinux.gz, stripped(?) and compressed arm64: Image, stripped and uncompressed armel,armhf: zImage, stripped and compressed hppa: vmlinux, UNstripped and uncompressed m68k: vmlinux.gz, stripped and compressed mips*: vmlinux, UNstripped and uncompressed powerpc*: vmlinux, UNstripped and uncompressed s390x: image, stripped and uncompressed sh4: zImage, stripped(?) and compressed sparc64: zImage, stripped and compressed x86: bzImage, stripped and compressed (No binary packages of 4.7 are available on ftp.debian-ports.org for alpha or sh4 yet, so those results are based on reading the respective Makefiles.) It seems that we only need a special case in debian/rules.real for those architectures where we install vmlinux directly. Ben. -- Ben Hutchings The first rule of tautology club is the first rule of tautology club. signature.asc Description: This is a digitally signed message part
Bug#838607: linux-image-4.7.0-0.bpo.1-amd64-unsigned: new file date writing issue
Package: linux-image-4.7.0-0.bpo.1-amd64-unsigned Version: 4.7.2-1~bpo8+1 Severity: normal There's a bug with ext4 on the new 4.7 kernel -- rare but it happened here on an ext4 mountpoint (/home /dev/md1 ext4 rw,relatime,data=ordered) when a new file is created, the "create time" is not properly set.(2014 was written as the create year instead of 2016) it occured today after I updated to 4.7 so I can only assume it has something to do with it.. my system here has "mdadm" containers, and perhaps it's possible a set of conditions allowed this rarity to occur.
Bug#838605: Enable PowerNV MTD modules on POWER systems
Package: linux-image-4.6.0-1-powerpc64le Version: 4.6.4-1 Severity: important The PowerNV MTD module is required for checkstop diagnostics on POWER8 and higher machines, but it is not enabled in the kernel build. Please enable it as a module with the following kernel .config lines: CONFIG_MTD=m CONFIG_MTD_POWERNV_FLASH=m Thanks!
Bug#838604: Enable opal-prd module on POWER systems
Package: linux-image-4.6.0-1-powerpc64le Version: 4.6.4-1 Severity: important The opal-prd module is required for checkstop diagnostics on POWER8 and higher machines, but it is not enabled in the kernel build. Please enable it as a module with the following kernel .config line: CONFIG_OPAL_PRD=m Thanks!
Bug#837588: hppa: Please disable CONFIG_FTRACE for hppa architecture
Hi Ben, On 19.09.2016 20:56, Ben Hutchings wrote: > On Mon, 2016-09-19 at 20:50 +0200, Helge Deller wrote: >> On 19.09.2016 19:41, Ben Hutchings wrote: >>> On Mon, 2016-09-12 at 20:28 +0100, Ben Hutchings wrote: On Mon, 2016-09-12 at 18:17 +0200, Helge Deller wrote: > > So, can you please deactivate CONFIG_FTRACE completely for 32- and > 64bit hppa configs? > Is it sufficient to add "CONFIG_FTRACE=n" to > debian/config/hppa/config ? Done. Argh - this didn't fixed the size issues on hppa. I was under the wrong assumption, that CONFIG_FTRACE (which was implemented in kernel 4.7 for the first time) was the culprit which increased the kernel size. This assumption was wrong. The attached patch finally fixes the issue. It re-enables the CONFIG_FTRACE option (which is set by your upper config files), and disables CONFIG_DEBUG_INFO which was now suddenly enabled by the debian kernel 4.7 (it wasn't in 4.6!). I enabled CONFIG_DEBUG_RODATA to write-protect kernel memory as well. The main problem was, that the generated dwarf debug info increases the kernel vmlinux image from 17MB to 97MB in disk size. I've compile- and run-tested the patch and built a +b1 kernel. Can you apply the attached patch on top of current git? I can commit it myself as well if you like. Thanks! Helge diff -up ./config/hppa/config.org ./config/hppa/config --- ./config/hppa/config.org 2016-09-21 21:34:30.894455256 +0200 +++ ./config/hppa/config 2016-09-22 20:48:48.314036351 +0200 @@ -571,15 +571,10 @@ CONFIG_SGETMASK_SYSCALL=y CONFIG_SYSFS_SYSCALL=y ## -## file: kernel/trace/Kconfig -## -#. As of 4.7 this has a huge size cost; see #837588 -# CONFIG_FTRACE is not set - -## ## file: lib/Kconfig.debug ## CONFIG_DEBUG_STACKOVERFLOW=y +CONFIG_DEBUG_RODATA=y # CONFIG_LOCKUP_DETECTOR is not set ## diff -up ./config/hppa/defines.org ./config/hppa/defines --- ./config/hppa/defines.org 2016-09-22 09:38:55.695723334 +0200 +++ ./config/hppa/defines 2016-09-22 09:38:36.771730760 +0200 @@ -6,6 +6,7 @@ kernel-arch: parisc image-file: vmlinux # linux-signed only works for architectures in the main archive signed-modules: false +debug-info: false [image] suggests: palo signature.asc Description: OpenPGP digital signature
Bug#827618: similar bug w/ linux-image-4.7.0-1-amd64{,-unsigned}
Hi, This time I replaced linux-image-4.7.0-1-amd64 w/ linux-image-4.7.0-1-amd64-unsigned. Then I ran: $ sudo aptitude purge ~c ... Purging configuration files for linux-image-4.7.0-1-amd64 (4.7.2-1+s1) ... ... rmdir: failed to remove '/lib/modules/4.7.0-1-amd64': Directory not empty ... Not only did this cause dpkg to fail, it also removed modules.alias etc. So replacing the signed kernel package with the unsigned one still causes some problems. - Felix signature.asc Description: PGP signature
