[valgrind] [Bug 451878] Add support for new syscall memfd_secret

2022-04-19 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=451878 Mark Wielaard changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED

[valgrind] [Bug 451878] Add support for new syscall memfd_secret

2022-04-18 Thread Di Chen
https://bugs.kde.org/show_bug.cgi?id=451878 --- Comment #3 from Di Chen --- Created attachment 148223 --> https://bugs.kde.org/attachment.cgi?id=148223=edit [patch v1] Support new memfd_secret linux syscall (447) This patch supports memfd_secret across these arches: arm64, amd64(x86_64),

[valgrind] [Bug 451878] Add support for new syscall memfd_secret

2022-04-06 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=451878 --- Comment #2 from Mark Wielaard --- Looks like my email about this to your @outlook.com address bounced. So just in case you didn't see it: Thanks, that applied fine. And I admit having been confused by memfd_create vs memfd_secret before. I have

[valgrind] [Bug 451878] Add support for new syscall memfd_secret

2022-03-30 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=451878 --- Comment #1 from di.che...@outlook.com --- Created attachment 147839 --> https://bugs.kde.org/attachment.cgi?id=147839=edit [patch] memfd test should be memfd_create test memfd test should be memfd_create test Currently, syscall memfd_create was

[valgrind] [Bug 451878] Add support for new syscall memfd_secret

2022-03-25 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=451878 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org -- You are receiving this mail

[valgrind] [Bug 451878] Add support for new syscall memfd_secret

2022-03-25 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=451878 di.che...@outlook.com changed: What|Removed |Added Assignee|jsew...@acm.org |di.che...@outlook.com -- You are