Your message dated Mon, 26 Dec 2022 19:59:54 +0000 with message-id <[email protected]> and subject line Re: Bug#919605: grub-fstest: segmentation fault with a very long value for '-n' option has caused the Debian Bug report #919605, regarding grub-fstest: segmentation fault with a very long value for '-n' option 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.) -- 919605: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919605 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: grub-common Severity: normal Dear maintainer, passing a very long value to grub-fstest command with '-n" option causes a segmentation fault. $ foo="0"; for i in {1..6000}; foo="$foo$i"; done $ grub-fstest -n $foo Segmentation fault Similarly: $ echo "$foo" > foofile $ grub-fstest -n $(cat foofile) Segmentation fault A more verbose output from tty1: $ grub-fstest -n $foo [ 2897.594543] grub-fstest[29069]: segfault at 0 ip 00005598771051db sp 00007ffe657517a0 error 4 in grub-fstest[559877104000+7b000] [ 2897.596081] Code: 05 71 c3 0d 00 01 31 c0 e9 72 fe ff ff 66 90 31 d2 48 8d 74 24 08 48 89 df e8 41 e2 05 00 48 8b 54 24 08 48 89 05 85 dc 0c 00 <80> 3a 73 0f 85 42 fe ff ff 48 c1 e0 09 48 89 05 71 dc 0c 00 31 c0 Segmentation fault Kind regards. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=en_US (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---Closing as requested! On Fri, Jan 18, 2019 at 06:22:03PM +0100, s3v wrote: >I can't reproduce this issue anymore (with long argument or long file). >Please feel free to close this bug, > >(I forgot to mention that my shell is Bash). > >Sorry for the noise and thanks for your time. > >Kind regards. -- Steve McIntyre, Cambridge, UK. [email protected] Who needs computer imagery when you've got Brian Blessed?
--- End Message ---
