linux-user: revert previous workaround for glibc >= 2.36
Status from this message: Applied to my linux-user-for-8.0 branch.
Get series with b4
b4 am [email protected]Versions newest first
Patches in v1 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | Revert "linux-user: add more compat ioctl definitions"linux-user/ | +0 | 0 replies | |
| 2/2 | Revert "linux-user: fix compat with glibc >= 2.36 sys/mount.h"linux-user/ meson.build | +0 | 0 replies |
Reviews trailers per patch
None of the 2 patches has a Reviewed-by or Acked-by of their own; the series has one for all of them.
| Patch | Marc-André Lureau |
|---|---|
| Series | R-b |
| 1/2 | |
| 2/2 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/2] linux-user: revert previous workaround for glibc >= 2.36
It didn't appear that glibc was going to fix the problem breaking includes of linux/mount.h vs sys/mount.h, so QEMU applied a workaround copying the symbols/structs we need into a local header.
Since then Linux modified linux/btrfs.h to pull in linux/fs.h which caused a clash with our workaround. Rather than invent workarounds for our workarounds, we can luckily just drop our previous workarounds. glibc has been fixed after all, and backported this fix to the stable 2.36 release series too. We should just expect distros to pull in the stable fix, which Fedora at least has already done.
Daniel P. Berrangé (2):
Revert "linux-user: add more compat ioctl definitions" Revert "linux-user: fix compat with glibc >= 2.36 sys/mount.h"
linux-user/syscall.c | 43 ------------------------------------------- meson.build | 2 -- 2 files changed, 45 deletions(-)
Signature · 1 line
2.38.1