On Fri, Jun 28, 2024 at 12:07 AM Aurelien Jarno <[email protected]> wrote:
> Hi, > > On 2024-06-27 10:44, Vishal Bhoj wrote: > > Package: libc6 > > Version: 2.38-13 > > Severity: important > > X-Debbugs-Cc: [email protected] > > > > Dear Maintainer, > > > > *** Reporter, please consider answering these questions, where > appropriate *** > > > > * What led up to the situation? > > Upgrading libc6 on testing has caused libguestfs usage. > > Thanks for your bug report. I am unable to reproduce your issue, here > the libguestfs-test-tool program returns: > > ===== TEST FINISHED OK ===== > > Therefore, could you please share the full output of that program so > that we can understand the problem? > I use debian testing in container. I have ran the below test case using docker and podman as well: $ docker run -it debian:testing root@9d14b1ceee4f:/# apt update root@9d14b1ceee4f:/# apt install -y libguestfs-tools root@9d14b1ceee4f:/# libguestfs-test-tool // Passes with libc 2.38.12 root@9d14b1ceee4f:/# apt install libc6 // updates libc to 2.38.13 root@9d14b1ceee4f:/# libguestfs-test-tools // fails . . . [ 2.498808] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100 [ 2.499156] CPU: 0 PID: 1 Comm: init Not tainted 6.8.12-amd64 #1 Debian 6.8.12-1 [ 2.499277] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 [ 2.500309] Call Trace: [ 2.500781] <TASK> [ 2.500894] panic+0x33b/0x360 [ 2.501120] do_exit+0x987/0xaf0 [ 2.501166] ? do_iter_readv_writev+0x151/0x1c0 [ 2.501219] do_group_exit+0x31/0x80 [ 2.501266] __x64_sys_exit_group+0x18/0x20 [ 2.501324] do_syscall_64+0x83/0x190 [ 2.501569] ? syscall_exit_to_user_mode+0x88/0x220 [ 2.501623] ? do_writev+0x7e/0x160 [ 2.501660] ? do_writev+0x7e/0x160 [ 2.501697] ? syscall_exit_to_user_mode+0x88/0x220 [ 2.501746] ? do_syscall_64+0x8f/0x190 [ 2.501786] ? do_writev+0x7e/0x160 [ 2.502782] ? do_writev+0x7e/0x160 [ 2.502821] ? syscall_exit_to_user_mode+0x88/0x220 [ 2.502870] ? do_syscall_64+0x8f/0x190 [ 2.502908] ? do_syscall_64+0x8f/0x190 [ 2.502947] ? __irq_exit_rcu+0x3b/0xc0 [ 2.502988] entry_SYSCALL_64_after_hwframe+0x78/0x80 [ 2.504127] RIP: 0033:0x4094ee [ 2.504359] Code: 00 00 48 8b 05 73 59 00 00 e9 81 fe ff ff 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 f3 0f 1e fa 48 63 ff b8 e7 00 00 00 0f 05 <ba> 3c 00 00 00 0f 1f 44 00 00 48 89 d0 0f 05 eb f9 90 f3 0f 1e fa [ 2.504557] RSP: 002b:00007ffc901cd868 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7 [ 2.505435] RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00000000004094ee [ 2.505530] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000001 [ 2.505599] RBP: 00007ffc901cd8c0 R08: fefefefefefefeff R09: 000000000000002a [ 2.506576] R10: 0000000000000006 R11: 0000000000000246 R12: 000000000040b20c [ 2.506650] R13: 00007f6e61228173 R14: 00007ffc901cd8b0 R15: 00000ffffff00000 [ 2.506750] </TASK> [ 2.507099] Kernel Offset: 0x1b600000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff) [ 2.507984] Rebooting in 1 seconds.. libguestfs: error: appliance closed the connection unexpectedly, see earlier error messages libguestfs: child_cleanup: 0x62967dcdbd80: child process died libguestfs: sending SIGTERM to process 21005 libguestfs: qemu maxrss 256472K libguestfs: error: guestfs_launch failed, see earlier error messages libguestfs: closing guestfs handle 0x62967dcdbd80 (state 0) libguestfs: command: run: rm libguestfs: command: run: \ -rf /tmp/libguestfsyfGib0 libguestfs: command: run: rm libguestfs: command: run: \ -rf /tmp/libguestfsWw8pYe root@9d14b1ceee4f:/# > Regards > Aurelien > > -- > Aurelien Jarno GPG: 4096R/1DDD8C9B > [email protected] http://aurel32.net > -- *Thanks & Regards,Vishal*
