Bug 1948645

Summary: [ARM 9 FEAT] Please enable MTE heap tagging support in glibc
Product: Red Hat Enterprise Linux 9 Reporter: Jeremy Linton (ARM) <jlinton>
Component: glibcAssignee: Florian Weimer <fweimer>
Status: CLOSED CURRENTRELEASE QA Contact: Sergey Kolosov <skolosov>
Severity: medium Docs Contact:
Priority: medium    
Version: 9.0CC: ashankar, codonell, dj, fweimer, mnewsome, pfrankli, sipoyare
Target Milestone: betaKeywords: FutureFeature, Patch, Triaged
Target Release: 9.0 Beta   
Hardware: aarch64   
OS: Linux   
Whiteboard:
Fixed In Version: glibc-2.33.9000-36.el9 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-12-07 21:42:00 UTC Type: Enhancement
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1958224    
Bug Blocks:    

Description Jeremy Linton (ARM) 2021-04-12 16:45:15 UTC 
Description of problem: Arm V8.5 CPUs are expected in the RHEL 9 timeframe, as such Glibc on aarch64 should be built with --enable-memory-tagging. A similar defect for fedora is here: 1944758

There is another more general (kernel focused) RHEL 9 defect: 1894743


Version-Release number of selected component (if applicable): 2.33-2
Comment 2 Florian Weimer 2021-04-16 13:55:37 UTC 
I assume this is just a simple spec file change, like this:

+ %ifarch aarch64
+ 		--enable-memory-tagging \
+ %endif

Can we do this for glibc 2.33, or should we wait until the rebase to glibc 2.34? Thanks.
Comment 4 Carlos O'Donell 2021-05-10 16:26:37 UTC 
(In reply to Florian Weimer from comment #2)
> I assume this is just a simple spec file change, like this:
> 
> + %ifarch aarch64
> + 		--enable-memory-tagging \
> + %endif
> 
> Can we do this for glibc 2.33, or should we wait until the rebase to glibc
> 2.34? Thanks.

We received feedback from Arm about this.

The answer to this is as follows:
- The 2.33 release has everything that we need to enable memory tagging and small fixes were backported into the release branch.
- That 2.34 has only performance improvements.

Therefore we can move this forward with glibc 2.33.