From: "me at serhei dot io" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/10280] allow relaxing of `uname -r` matching runtime assertion ro ABI-compatible kernel series
Date: Thu, 14 May 2020 21:35:45 +0000 [thread overview]
Message-ID: <bug-10280-6586-KnkJMEEcK0@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-10280-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=10280
--- Comment #7 from Serhei Makarov <me at serhei dot io> ---
Re-enabled the strict vermagic check for guru-mode scripts
after investigating PR24720 and re-testing the patch on PPC.
Also disabled the vacuous UTS_VERSION/UTS_RELEASE checks unless enabled with
STP_ENABLE_VERREL_CHECK.
Before closing the PR, should give a bit of time to see what happens in
testing,
and document in NEWS that the UTS_VERSION/UTS_RELEASE check setting is now
controlled with STP_ENABLE_VERREL_CHECK.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2020-05-14 21:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-10280-6586@http.sourceware.org/bugzilla/>
2017-11-28 15:44 ` fche at redhat dot com
2019-01-16 19:18 ` me at serhei dot io
2019-06-13 23:48 ` fche at redhat dot com
2020-02-14 14:10 ` fweimer at redhat dot com
2020-02-19 21:10 ` fche at redhat dot com
2020-03-18 16:19 ` me at serhei dot io
2020-05-14 21:35 ` me at serhei dot io [this message]
2020-05-20 20:35 ` me at serhei dot io
2020-05-20 20:35 ` me at serhei dot io
2009-06-14 14:41 [Bug translator/10280] New: allow relaxing of `uname -r` matching runtime assertion fche at redhat dot com
2009-07-02 13:55 ` [Bug translator/10280] allow relaxing of `uname -r` matching runtime assertion ro ABI-compatible kernel series fche at redhat 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-10280-6586-KnkJMEEcK0@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@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).