Fix valgrind for glibc-2.39, Linux 6.4, and binutils-2.42

[Douglas R. Reno]

The combination of these three packages are causing some problems to occur on both x86 and x86_64. In the case of x86, the problems are due to new nop patterns that were introduced with binutils-2.42. In the case of both architectures, the fchmodat2() syscall was added in Linux 6.4.x, and then support for it was added in glibc-2.39. Because of this we will encounter errors like the following:

--701226-- WARNING: unhandled amd64-linux syscall: 452
--701226-- You may be able to write your own handler.
--701226-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--701226-- Nevertheless we consider this a bug.  Please report
--701226-- it at http://valgrind.org/support/bug_reports.html.

There are a few upstream bugs for this, but here's the two which are most relevant to these two bugs:

​https://bugs.kde.org/show_bug.cgi?id=477198 - fchmodat2() addition

​https://bugs.kde.org/show_bug.cgi?id=478624 and ​https://bugs.kde.org/show_bug.cgi?id=480680 - x86 nop issue

It looks like Debian, Gentoo, Arch, and Fedora are now carrying patches for these bugs as well.

[Douglas R. Reno]

Fixed at 7c0429eaa4f9c2358945df9e2720837a151c0364