From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Herbert Xu <herbert@gondor.apana.org.au>,
Linux Crypto List <linux-crypto@vger.kernel.org>
Cc: Chengfeng Ye <cyeaa@connect.ust.hk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: Fixes tags need some work in the crypto tree
Date: Tue, 23 Nov 2021 08:29:25 +1100 [thread overview]
Message-ID: <20211123082925.068ff4e8@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1178 bytes --]
Hi all,
In commit
e9c195aaeed1 ("crypto: qce - fix uaf on qce_skcipher_register_one")
Fixes tag
Fixes: ec8f5d8f ("crypto: qce - Qualcomm crypto engine driver")
has these problem(s):
- SHA1 should be at least 12 digits long
Can be fixed by setting core.abbrev to 12 (or more) or (for git v2.11
or later) just making sure it is not set (or set to "auto").
In commit
b4cb4d316319 ("crypto: qce - fix uaf on qce_ahash_register_one")
Fixes tag
Fixes: ec8f5d8f ("crypto: qce - Qualcomm crypto engine driver")
has these problem(s):
- SHA1 should be at least 12 digits long
Can be fixed by setting core.abbrev to 12 (or more) or (for git v2.11
or later) just making sure it is not set (or set to "auto").
In commit
4a9dbd021970 ("crypto: qce - fix uaf on qce_aead_register_one")
Fixes tag
Fixes: 9363efb4 ("crypto: qce - Add support for AEAD algorithms")
has these problem(s):
- SHA1 should be at least 12 digits long
Can be fixed by setting core.abbrev to 12 (or more) or (for git v2.11
or later) just making sure it is not set (or set to "auto").
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2021-11-22 21:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 21:29 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-09-10 14:51 linux-next: Fixes tags need some work in the crypto tree Stephen Rothwell
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=20211123082925.068ff4e8@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=cyeaa@connect.ust.hk \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).