[glibc] Don't write beyond destination in __mempcpy_avx512_no_vzeroupper
Bug #1776124 reported by
quanxian
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| intel |
Fix Released
|
Medium
|
Unassigned | ||
| Ubuntu |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
Description:
a corner case with glibc code that causes KNL/KNM system hang.
"
Don't write beyond destination in __mempcpy_
When compiled as mempcpy, the return value is the end of the destination
buffer, thus it cannot be used to refer to the start of it.
"
Here is the commit for this issue.
18.04 and 19.04 need backport this patch into glibc.
Details:
For details, please refer to:
http://
http://
https:/
Target Package: glibc
Target Release: 18.04.x/18.10
| description: | updated |
| tags: | added: intel-upkg-18.10 |
| tags: | added: intel-upkg-18.04 |
| description: | updated |
Revision history for this message
| Joseph Salisbury (jsalisbury) wrote | #1 |
| Changed in intel: | |
| importance: | Undecided → Medium |
| status: | New → Triaged |
| tags: | added: kernel-da-key |
Revision history for this message
| quanxian (quanxian-wang) wrote | #2 |
| information type: | Proprietary → Public |
| tags: |
added: intel-upkg-19.04 removed: intel-upkg-18.10 |
| description: | updated |
Revision history for this message
| quanxian (quanxian-wang) wrote | #3 |
| Changed in ubuntu: | |
| status: | New → Fix Released |
| Changed in intel: | |
| status: | Triaged → Fix Released |
To post a comment you must log in.
Can we move this bug to the "Linux" package and make it public?