From: ismaell <ismaell@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] qemu: Fix padding in host_sigevent
Date: Sat, 11 Sep 2021 21:02:03 +0200 [thread overview]
Message-ID: <20210911190203.r_cWyn_ZQUk5lROnEiORL1gsKVr1IxoCmrD1xQ8Y528@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32897@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 799 bytes --]
There is an updated pull request by ismaell against master on the void-packages repository
https://github.com/ismaell/void-packages patch-1
https://github.com/void-linux/void-packages/pull/32897
qemu: Fix padding in host_sigevent
<!-- Mark items with [x] where applicable -->
#### General
- [x] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR
A patch file from https://github.com/void-linux/void-packages/pull/32897.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-patch-1-32897.patch --]
[-- Type: text/x-diff, Size: 1105 bytes --]
From 4e0ab7d2eb5491ac6aef3bc7f35ce2d5ee0f1f0a Mon Sep 17 00:00:00 2001
From: Ismael Luceno <ismael@iodev.co.uk>
Date: Thu, 9 Sep 2021 23:15:02 +0200
Subject: [PATCH] qemu: Fix padding in host_sigevent
The struct should be padded to 64 bytes but instead it was padded to
(sizeof(int) * (64 - 2 * sizeof(int) + sizeof(union sigval))).
Assuming both int and pointer types are 64 bits, that leads to a padding
of 448 bytes.
---
srcpkgs/qemu/patches/musl-fix-sigevent-and-sigval_t.patch | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/srcpkgs/qemu/patches/musl-fix-sigevent-and-sigval_t.patch b/srcpkgs/qemu/patches/musl-fix-sigevent-and-sigval_t.patch
index c51fca6cf432..3b0754b478bf 100644
--- a/srcpkgs/qemu/patches/musl-fix-sigevent-and-sigval_t.patch
+++ b/srcpkgs/qemu/patches/musl-fix-sigevent-and-sigval_t.patch
@@ -10,7 +10,7 @@
+ int sigev_signo;
+ int sigev_notify;
+ union {
-+ int _pad[64-sizeof(int) * 2 + sizeof(union sigval)];
++ int _pad[(64 - (sizeof(int) * 2 + sizeof(union sigval))) / sizeof(int)];
+ int _tid;
+ } _sigev_un;
+};
next prev parent reply other threads:[~2021-09-11 19:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-09 21:17 [PR PATCH] " ismaell
2021-09-09 23:25 ` ismaell
2021-09-09 23:25 ` [PR PATCH] [Closed]: " ismaell
2021-09-09 23:36 ` ismaell
2021-09-09 23:37 ` ismaell
2021-09-10 14:25 ` ericonr
2021-09-11 0:43 ` ismaell
2021-09-11 19:02 ` ismaell [this message]
2021-09-11 19:03 ` ismaell
2021-09-11 22:45 ` ericonr
2021-09-11 22:45 ` ericonr
2021-09-18 15:39 ` [PR PATCH] [Updated] " ismaell
2021-09-18 15:40 ` ismaell
2021-09-18 15:41 ` [PR PATCH] [Updated] " ismaell
2021-09-19 3:08 ` ericonr
2021-09-19 14:39 ` [PR PATCH] [Updated] " ismaell
2021-09-19 14:40 ` ismaell
2021-09-20 0:53 ` [PR PATCH] [Merged]: " ericonr
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=20210911190203.r_cWyn_ZQUk5lROnEiORL1gsKVr1IxoCmrD1xQ8Y528@z \
--to=ismaell@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).