intel
Bump cryptography from 42.0.2 to 42.0.4 in /llvm/utils/git
Bumps cryptography from 42.0.2 to 42.0.4.
Changelog
Sourced from cryptography's changelog.
42.0.4 - 2024-02-20
* Fixed a null-pointer-dereference and segfault that could occur when creating a PKCS#12 bundle. Credit to **Alexander-Programming** for reporting the issue. **CVE-2024-26130** * Fixed ASN.1 encoding for PKCS7/SMIME signed messages. The fields ``SMIMECapabilities`` and ``SignatureAlgorithmIdentifier`` should now be correctly encoded according to the definitions in :rfc:`2633` :rfc:`3370`... _v42-0-3:
42.0.3 - 2024-02-15
- Fixed an initialization issue that caused key loading failures for some users.
.. _v42-0-2:
Commits
fe18470Bump for 42.0.4 release (#10445)aaa2dd0Fix ASN.1 issues in PKCS#7 and S/MIME signing (#10373) (#10442)7a4d012Fixes #10422 -- don't crash when a PKCS#12 key and cert don't match (#10423) ...df314bbbackport actions m1 switch to 42.0.x (#10415)c49a7a5changelog and version bump for 42.0.3 (#10396)396bcf6fix provider loading take two (#10390) (#10395)0e0e46fbackport: initialize openssl's legacy provider in rust (#10323) (#10333)- See full diff in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
-
@dependabot rebasewill rebase this PR -
@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it -
@dependabot mergewill merge this PR after your CI passes on it -
@dependabot squash and mergewill squash and merge this PR after your CI passes on it -
@dependabot cancel mergewill cancel a previously requested merge and block automerging -
@dependabot reopenwill reopen this PR if it is closed -
@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency -
@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the Security Alerts page.
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "Published by a pub.dev verified publisher"){kind=small}
@intel/dpcpp-devops-reviewers, @intel/llvm-reviewers-runtime, any ideas what could cause this error:
lit.py: D:\github\_work\llvm\llvm\llvm\sycl\test-e2e\lit.cfg.py:613: fatal: Cannot list device aspects for level_zero:gpu
Command ' d:\github\_work\llvm\llvm\install\bin\sycl-ls.exe --verbose' returned non-zero exit status 3221225477.
stdout:[level_zero:gpu] Intel(R) Level-Zero, Intel(R) Iris(R) Xe Graphics 1.3 [1.3.28044]
At the same time sycl-ls --verbose worked in the same workflow
Platforms: 2
Platform [#1]:
Version : 1.3
Name : Intel(R) Level-Zero
Vendor : Intel(R) Corporation
Devices : 1
Device [#0]:
Type : gpu
Version : 1.3
Name : Intel(R) Iris(R) Xe Graphics
Vendor : Intel(R) Corporation
Driver : 1.3.28044
Aspects : gpu fp16 online_compiler online_linker queue_profiling usm_device_allocations usm_host_allocations usm_shared_allocations ext_intel_pci_address ext_intel_gpu_eu_count ext_intel_gpu_eu_simd_width ext_intel_gpu_slices ext_intel_gpu_subslices_per_slice ext_intel_gpu_eu_count_per_subslice atomic64 ext_intel_device_info_uuid ext_intel_gpu_hw_threads_per_eu ext_intel_free_memory ext_intel_device_id ext_intel_memory_clock_rate ext_intel_memory_bus_width ext_intel_legacy_image ext_intel_esimd ext_oneapi_ballot_group ext_oneapi_fixed_size_group ext_oneapi_opportunistic_group ext_oneapi_tangle_group
info::device::sub_group_sizes: 8 16 32
Platform [#2]:
Version : OpenCL 3.0
Name : Intel(R) OpenCL Graphics
Vendor : Intel(R) Corporation
Devices : 1
Device [#0]:
Type : gpu
Version : OpenCL 3.0 NEO
Name : Intel(R) Iris(R) Xe Graphics
Vendor : Intel(R) Corporation
Driver : 31.0.101.[51](https://github.com/intel/llvm/actions/runs/7995714644/job/21837847032#step:10:52)86
Aspects : gpu fp16 online_compiler online_linker queue_profiling usm_device_allocations usm_host_allocations usm_shared_allocations atomic[64](https://github.com/intel/llvm/actions/runs/7995714644/job/21837847032#step:10:65) ext_oneapi_srgb ext_intel_device_id ext_intel_legacy_image ext_intel_esimd ext_oneapi_ballot_group ext_oneapi_fixed_size_group ext_oneapi_opportunistic_group ext_oneapi_tangle_group
info::device::sub_group_sizes: 8 16 32
default_selector() : gpu, Intel(R) Level-Zero, Intel(R) Iris(R) Xe Graphics 1.3 [1.3.2[80](https://github.com/intel/llvm/actions/runs/7995714644/job/21837847032#step:10:81)44]
accelerator_selector() : No device of requested type available. -1 (PI_ERRO...
cpu_selector() : No device of requested type available. -1 (PI_ERRO...
gpu_selector() : gpu, Intel(R) Level-Zero, Intel(R) Iris(R) Xe Graphics 1.3 [1.3.28044]
custom_selector(gpu) : gpu, Intel(R) Level-Zero, Intel(R) Iris(R) Xe Graphics 1.3 [1.3.28044]
custom_selector(cpu) : No device of requested type available. -1 (PI_ERRO...
custom_selector(acc) : No device of requested type available. -1 (PI_ERRO...
Full log: https://github.com/intel/llvm/actions/runs/7995714644/job/21837847032
@intel/dpcpp-devops-reviewers, @intel/llvm-reviewers-runtime, any ideas what could cause this error:
It is weird that the first run works and the second doesn't. My guess is that the driver/hardware is left in a bad state after the first run. I've seen that happening before in PVC, but I don't remember it for Gen12. Still, I think it's worth checking locally to see if that's the issue.
This failure is not related to patch, so I'm going to merge it.
Still, I think it's worth checking locally to see if that's the issue.
Can someone from @intel/dpcpp-devops-reviewers follow-up on this?
Post-commit fails:
Complete job name: e2e-lin (Intel Arc A-Series Graphics with Level Zero, ["Linux", "arc"], --param matrix-xmx8=True ... / Intel Arc A-Series Graphics with Level Zero
Failed Tests (2): SYCL :: Config/select_device.cpp SYCL :: ESIMD/unified_memory_api/scatter_lacc_dg2_pvc.cpp
Complete job name: e2e-win / Intel GEN12 Graphics with Level Zero
Failed Tests (8): SYCL :: Assert/assert_in_kernels_win.cpp SYCL :: Assert/assert_in_multiple_tus_one_ndebug_win.cpp SYCL :: Assert/assert_in_multiple_tus_win.cpp SYCL :: Assert/assert_in_one_kernel_win.cpp SYCL :: Assert/assert_in_simultaneous_kernels_win.cpp SYCL :: Assert/assert_in_simultaneously_multiple_tus.cpp SYCL :: Assert/assert_in_simultaneously_multiple_tus_one_ndebug.cpp SYCL :: Plugin/sycl-ls-unified-runtime.cpp
This failure is not related to patch, so I'm going to merge it.
Still, I think it's worth checking locally to see if that's the issue.
Can someone from @intel/dpcpp-devops-reviewers follow-up on this?
I hit this issue again in post-commit - https://github.com/intel/llvm/actions/runs/8087099887/job/22099917679. It's on the same runner - intel_sycl119893. It sounds like a potential issue with the environment.
UPDATE: I'm not the only one - https://github.com/intel/llvm/actions/runs/8084473526/job/22091081873 - pre-commit for https://github.com/intel/llvm/pull/12855. The same runner.
I just saw the sycl-ls issue again in https://github.com/intel/llvm/actions/runs/8180367243/job/22368716100?pr=12925. Note that the runner is different this time: intel_sycl05.
Another failure with runner intel_sycl05: https://github.com/intel/llvm/actions/runs/8156710255/job/22297115170?pr=12582