From: Bhaskar Chowdhury <unixbhaskar@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Ronald Warsow <rwarsow@gmx.de>,
stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: stable kernel checksumming fails
Date: Mon, 8 Mar 2021 04:29:41 +0530 [thread overview]
Message-ID: <YEVa3dLvugd4+9Cv@OpenSuse> (raw)
In-Reply-To: <YETm+6sQqek6kY/A@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 2364 bytes --]
On 15:45 Sun 07 Mar 2021, Greg KH wrote:
>On Sun, Mar 07, 2021 at 03:10:49PM +0100, Ronald Warsow wrote:
>> hello
>>
>> getting stable kernels with this script:
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/mricon/korg-helpers.git/tree/get-verified-tarball
>>
>>
>> fails since the last 2 (?) stable releases with (last lines):
>>
>> ...
>>
>> + /usr/bin/curl -L -o
>> /home/ron/Downloads/linux-tarball-verify.1GiZid5WT.untrusted/linux-5.11.4.tar.xz
>> https://cdn.kernel.org/pub/linux/kernel/v5.x/linux-5.11.4.tar.xz
>> % Total % Received % Xferd Average Speed Time Time Time
>> Current
>> Dload Upload Total Spent Left
>> Speed
>> 100 112M 100 112M 0 0 5757k 0 0:00:19 0:00:19 --:--:--
>> 5938k
>>
>> pushd ${TMPDIR} >/dev/null
>> + pushd /home/ron/Downloads/linux-tarball-verify.1GiZid5WT.untrusted
>> echo "Verifying checksum on linux-${VER}.tar.xz"
>> + echo 'Verifying checksum on linux-5.11.4.tar.xz'
>> Verifying checksum on linux-5.11.4.tar.xz
>> if ! ${SHA256SUMBIN} -c ${SHACHECK}; then
>> echo "FAILED to verify the downloaded tarball checksum"
>> popd >/dev/null
>> rm -rf ${TMPDIR}
>> exit 1
>> fi
>> + /usr/bin/sha256sum -c
>> /home/ron/Downloads/linux-tarball-verify.1GiZid5WT.untrusted/sha256sums.txt
>> /usr/bin/sha256sum:
>> /home/ron/Downloads/linux-tarball-verify.1GiZid5WT.untrusted/sha256sums.txt:
>> no properly formatted SHA256 checksum lines found
>> + echo 'FAILED to verify the downloaded tarball checksum'
>> FAILED to verify the downloaded tarball checksum
>> + popd
>> + rm -rf /home/ron/Downloads/linux-tarball-verify.1GiZid5WT.untrusted
>> + exit 1
>>
>>
>> checksumming the downloaded kernel manually gives an "Okay" though.
>>
>>
>> is this just me (on Fedora 33) ?
>
>Fails for me on Arch:
>
>Verifying checksum on linux-5.11.4.tar.xz
>/usr/bin/sha256sum: /home/gregkh/Downloads/linux-tarball-verify.gZo313NCk.untrusted/sha256sums.txt: no properly formatted SHA256 checksum lines found
>FAILED to verify the downloaded tarball checksum
>
I can confirm it works alright with me on OpenSuse Tumbleweed and Slackware
...yet to test on others....Debian....Arch and Gentoo ...
>
Oh btw ...sometimes I got that specific error because of lack of dns
propogation to dns stuff in some reason...
>Konstantin, anything change recently?
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2021-03-07 23:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-07 14:10 stable kernel checksumming fails Ronald Warsow
2021-03-07 14:45 ` Greg KH
2021-03-07 15:43 ` Konstantin Ryabitsev
2021-03-07 15:48 ` Greg KH
2021-03-07 18:28 ` Ronald Warsow
2021-03-07 22:59 ` Bhaskar Chowdhury [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YEVa3dLvugd4+9Cv@OpenSuse \
--to=unixbhaskar@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=konstantin@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rwarsow@gmx.de \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.