Bug#1073998: linux: Purging linux-image- doesn't clean up modules.weakdep file

2024-06-21 Thread Christoph Berg
Re: Diederik de Haas
> When removing or 'even' purging a linux-image- package, it
> reports the following issue:
> 
> rmdir: failed to remove '/lib/modules/': Directory not empty
> 
> The reason for that is that there's still a ``modules.weakdep`` file.

I just had the same problem on linux-image-6.6.15-amd64.

> It seems to me that at least with purging that file should be removed
> and subsequently the ``/lib/modules/`` dir.

TBH, I'd even argue plain "remove" should remove the debris from the
modules directory, it's not like there's anything of value in the
modules.* files left behind.

Kernels are the only package that I'm actually purging, if "remove"
wouldn't leave /lib/modules/*/ behind, I wouldn't have to do that.

Christoph



reassign 1064838 to linux

2024-02-26 Thread Christoph Berg
reassign 1064838 linux 
thanks


Christoph



Re: Processed: Re: Bug#1064838: New package names break APT safety features, ability to co-install different ABIs

2024-02-26 Thread Christoph Berg
Control: reassign -1 linux

Re: Debian Bug Tracking System
> Processing control commands:
> 
> > reassign -1 tech-ctte
> Bug #1064838 [src:linux] New package names break APT safety features, ability 
> to co-install different ABIs

Please only reassign to tech-ctte after the actual discussion has
finished with an open dispute. I see you have open questions to Julian
in the bug.

Christoph



Bug#1058937: /usr-move: Do we support upgrades without apt?

2023-12-21 Thread Christoph Berg
Re: Helmut Grohne
> Is it ok to call upgrade scenarios failures that cannot be reproduced
> using apt unsupported until we no longer deal with aliasing?
> 
> If the answer is yes here, we'll close #1058937 (Ben's libnfsidmap1 bug)
> with no action calling the scenario unsupported.

I think we should only deal with problems that can reasonably happen
in practice. If an extra hammer is required to hit the problem, we
should not spend extra effort on it.

Christoph



Re: AX.25 in the kernel

2019-08-06 Thread Christoph Berg
Re: Iain Learmonth 2019-08-06 <7285bc5a-e1e4-4c65-d75e-79a888101...@debian.org>
> This looks like a sensible option. Is there some man page or
> documentation about what that file should look like?

I think it's just one module per line:

$ cat /etc/modules-load.d/cups-filters.conf
# Parallel printer driver modules loading for cups
# LOAD_LP_MODULE was 'yes' in /etc/default/cups
lp
ppdev
parport_pc

Christoph



Re: AX.25 in the kernel

2019-08-06 Thread Christoph Berg
Re: Iain Learmonth 2019-08-06 <6d586162-d416-c753-1cc7-e72da4864...@debian.org>
> If you have ideas on how to re-enable module autoloading for hamradio
> protocols when libax25 is installed then please let me know.

/etc/modules-load.d/ax25.conf

... but it should probably depend on some debconf question.

Christoph



Bug#797530: 32bit pie memory layout leaves only ~100MB between heap and stack

2016-10-28 Thread Christoph Berg
More details:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1518483

Christoph



Bug#797530: 32bit pie memory layout leaves only ~100MB between heap and stack

2015-08-31 Thread Christoph Berg
Source: linux
Version: 3.16.7-ckt11-1
Severity: important

I'm still seeing a memory layout for pie executables on 32 bit that
only leaves a bit over 100MB between heap and stack:

$ uname -a
Linux feynman 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1 (2015-05-24) x86_64 
GNU/Linux

$ ./pie
f756b000-f756c000 rw-p  00:00 0
f756c000-f76d7000 r-xp  fe:00 11214  
/lib/i386-linux-gnu/libc-2.19.so
f76d7000-f76d9000 r--p 0016b000 fe:00 11214  
/lib/i386-linux-gnu/libc-2.19.so
f76d9000-f76da000 rw-p 0016d000 fe:00 11214  
/lib/i386-linux-gnu/libc-2.19.so
f76da000-f76dd000 rw-p  00:00 0
f76e6000-f76e8000 rw-p  00:00 0
f76e8000-f76e9000 r-xp  00:00 0  [vdso]
f76e9000-f76eb000 r--p  00:00 0  [vvar]
f76eb000-f770a000 r-xp  fe:00 11211  
/lib/i386-linux-gnu/ld-2.19.so
f770a000-f770b000 r--p 0001f000 fe:00 11211  
/lib/i386-linux-gnu/ld-2.19.so
f770b000-f770c000 rw-p 0002 fe:00 11211  
/lib/i386-linux-gnu/ld-2.19.so
f770c000-f770d000 r-xp  fe:02 392551 
/cb/cb/pie
f770d000-f770e000 rw-p  fe:02 392551 
/cb/cb/pie
f9119000-f913a000 rw-p  00:00 0  [heap]
ffcc4000-ffce5000 rw-p  00:00 0  [stack]

>>> 0xffcc4000-0xf913a000
112762880

$ cat pie.c
#define _GNU_SOURCE
#include 
#include 
   #include 
   #include 

int main (void)
{
  char *cmd;
  asprintf (&cmd, "cat /proc/%u/maps", getpid());
  return system(cmd);
}

$ gcc -m32 -pie -fpie pie.c -o pie

I thought this was fixed via this commit, but apparently it's not:

linux (3.16.7-ckt11-1) jessie; urgency=medium
- fs/binfmt_elf.c: fix bug in loading of PIE binaries

http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a87938b2e246b81b4fb713edb371a9fa3c5c3c86

This patch is in 3.16.7-ckt11-1, but apparently it doesn't fix this
issue.


FTR, 4.1 looks fine:

56594000-56595000 r-xp  fe:02 14443300   
/home/cbe/tmp/pie
56595000-56596000 rw-p  fe:02 14443300   
/home/cbe/tmp/pie
58166000-58187000 rw-p  00:00 0  [heap]
f756a000-f756b000 rw-p  00:00 0 
f756b000-f76d7000 r-xp  fe:02 20846504   
/lib/i386-linux-gnu/libc-2.19.so
f76d7000-f76d9000 r--p 0016c000 fe:02 20846504   
/lib/i386-linux-gnu/libc-2.19.so
f76d9000-f76da000 rw-p 0016e000 fe:02 20846504   
/lib/i386-linux-gnu/libc-2.19.so
f76da000-f76dd000 rw-p  00:00 0 
f76e6000-f76e8000 rw-p  00:00 0 
f76e8000-f76ea000 r--p  00:00 0  [vvar]
f76ea000-f76eb000 r-xp  00:00 0  [vdso]
f76eb000-f770a000 r-xp  fe:02 20844426   
/lib/i386-linux-gnu/ld-2.19.so
f770a000-f770b000 r--p 0001f000 fe:02 20844426   
/lib/i386-linux-gnu/ld-2.19.so
f770b000-f770c000 rw-p 0002 fe:02 20844426   
/lib/i386-linux-gnu/ld-2.19.so
ff976000-ff997000 rw-p  00:00 0  [stack]

Linux benz 4.1.0-1-amd64 #1 SMP Debian 4.1.3-1 (2015-08-03) x86_64 GNU/Linux

Christoph
-- 
c...@df7cb.de | http://www.df7cb.de/


signature.asc
Description: Digital signature


Bug#739593: unshare -m aka unshare(CLONE_NEWNS) mounts are visible globally

2014-02-20 Thread Christoph Berg
Source: linux
Version: 3.12.9-1
Severity: important

Mounts done in a unshare(CLONE_NEWNS) or unshare -m environment are
globally visible, and are not automatically removed once the process
exits:

$ mount | grep foobar
$ sudo unshare -m -- mount -t tmpfs foobar /tmp
$ mount | grep foobar
foobar on /tmp type tmpfs (rw,relatime)

This system is running systemd 204-6.

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (700, 'testing'), (150, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.12-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Christoph
-- 
c...@df7cb.de | http://www.df7cb.de/


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20140220093955.ga19...@msgid.df7cb.de



Bug#403526: Description is uninformative

2006-12-17 Thread Christoph Berg
Package: linux-support-2.6.18-3
Version: 2.6.18-8
Severity: minor

> Package: linux-support-2.6.18-3
> Source: linux-2.6
> Description: Support files for Linux 2.6.18
>  This package provides support files for the Linux kernel build.

After reading this, I still don't know what the package does. Could
you extend the description such that it doesn't merely repeat the
package name?

Thanks, Christoph
-- 
[EMAIL PROTECTED] | http://www.df7cb.de/


signature.asc
Description: Digital signature