public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "honggyu.kp at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/27300] GLIBC_TUNABLES=glibc.cpu.hwcaps=-IBT,-SHSTK not working
Date: Mon, 01 Feb 2021 21:52:13 +0000	[thread overview]
Message-ID: <bug-27300-131-Hr5LuxEU79@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27300-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=27300

--- Comment #6 from Honggyu Kim <honggyu.kp at gmail dot com> ---
(In reply to H.J. Lu from comment #5)
> (In reply to Honggyu Kim from comment #4)
> > (In reply to H.J. Lu from comment #3)
> > > Please use Ubuntu 20.10 or verify that all patches on users/hjl/cet/2.31
> > > branch at:
> > > 
> > > https://gitlab.com/x86-glibc/glibc/-/tree/users/hjl/cet/2.31
> > > 
> > > have been applied in glibc in Ubuntu 20.04.
> > 
> > Thanks for the quick reply. Does it mean that they are not applied in Ubuntu
> > 20.04 so it makes the problem? If so, is there any way to avoid this problem?
> > 
> > I don't have a machine that has Ubuntu 20.10 so will test it after setting
> > it up. Thanks very much for your help.
> 
> Please disable CET under Ubuntu 20.04

Thanks but how can I disable CET?

> or use Ubuntu 20.10.

The thing is that we want to support uftrace tool to cover all the distros
including Ubuntu 20.04. Our users cannot properly use the specific feature due
to this problem.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2021-02-01 21:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-31 23:34 [Bug libc/27300] New: " honggyu.kp at gmail dot com
2021-01-31 23:36 ` [Bug libc/27300] " honggyu.kp at gmail dot com
2021-01-31 23:37 ` honggyu.kp at gmail dot com
2021-01-31 23:39 ` honggyu.kp at gmail dot com
2021-01-31 23:39 ` honggyu.kp at gmail dot com
2021-01-31 23:47 ` hjl.tools at gmail dot com
2021-01-31 23:48 ` hjl.tools at gmail dot com
2021-02-01  8:42 ` honggyu.kp at gmail dot com
2021-02-01 21:41 ` hjl.tools at gmail dot com
2021-02-01 21:52 ` honggyu.kp at gmail dot com [this message]
2021-02-01 22:23 ` hjl.tools at gmail dot com
2021-02-01 23:42 ` honggyu.kp at gmail dot com
2021-02-04 21:34 ` honggyu.kp at gmail dot com
2021-02-04 22:54 ` hjl.tools at gmail dot com

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=bug-27300-131-Hr5LuxEU79@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).