From: "sipdbg at hacari dot net" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/26689] New: [mm] systemtap broken on >=5.8 (debian-testing): need portage from mmap_sem to mmap_lock API
Date: Thu, 01 Oct 2020 10:38:05 +0000 [thread overview]
Message-ID: <bug-26689-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=26689
Bug ID: 26689
Summary: [mm] systemtap broken on >=5.8 (debian-testing): need
portage from mmap_sem to mmap_lock API
Product: systemtap
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: runtime
Assignee: systemtap at sourceware dot org
Reporter: sipdbg at hacari dot net
Target Milestone: ---
Created attachment 12879
--> https://sourceware.org/bugzilla/attachment.cgi?id=12879&action=edit
debian-testing 5.8 kernel fix
Hi,
down_read (&mm->mmap_sem);
has evolved to
mmap_read_lock (mm);
Same things for up_{read,write} and *_trylock()
I fixed the source code and I am providing a patch.
Thanks you :-))
P.S.: I also included generated/utsrelease.h instead of linux/vermagic.h to
avoid an new pre-processor #error statement
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2020-10-01 10:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-01 10:38 sipdbg at hacari dot net [this message]
2020-10-01 13:17 ` [Bug runtime/26689] " 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-26689-6586@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).