From: Thomas Huth <thuth@redhat.com>
To: Bongsu Jeon <bongsu.jeon@samsung.com>, David Heidelberg <david@ixit.cz>
Cc: Shuah Khan <shuah@kernel.org>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
oe-linux-nfc@lists.linux.dev
Subject: Re: [PATCH] selftests: nci: Fix wrong size of status variables in nci_dev test
Date: Thu, 13 Aug 2026 16:45:02 +0200 [thread overview]
Message-ID: <68b1d486-37a9-43d4-a02f-66fa4689d437@redhat.com> (raw)
In-Reply-To: <20260710112300.512433-1-thuth@redhat.com>
On 10/07/2026 13.23, Thomas Huth wrote:
> From: Thomas Huth <thuth@redhat.com>
>
> pthread_join() stores the thread's return value (a "void *", i.e.
> 8 bytes on 64 bit computers) into the address of "status", but the
> "status" variable is declared as "int" with only 4 bytes. The extra
> four bytes clobber whatever is adjacent on the stack, which could
> silently corrupt other local variables. Use "intptr_t" to declare
> the "status" variables with the correct size.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> tools/testing/selftests/nci/nci_dev.c | 13 +++++++------
> 1 file changed, 7 insertions(+), 6 deletions(-)
>
> diff --git a/tools/testing/selftests/nci/nci_dev.c b/tools/testing/selftests/nci/nci_dev.c
> index 312f84ee0444f..4e7a5856f7ea3 100644
> --- a/tools/testing/selftests/nci/nci_dev.c
> +++ b/tools/testing/selftests/nci/nci_dev.c
> @@ -6,6 +6,7 @@
> * Test code for nci
> */
>
> +#include <stdint.h>
> #include <stdlib.h>
> #include <errno.h>
> #include <string.h>
> @@ -404,7 +405,7 @@ FIXTURE_SETUP(NCI)
> struct msgtemplate msg;
> pthread_t thread_t;
> __u32 event_group;
> - int status;
> + intptr_t status;
> int rc;
>
> self->open_state = false;
> @@ -497,7 +498,7 @@ static void *virtual_deinit_v2(void *data)
> FIXTURE_TEARDOWN(NCI)
> {
> pthread_t thread_t;
> - int status;
> + intptr_t status;
> int rc;
>
> if (self->open_state) {
> @@ -585,7 +586,7 @@ int start_polling(int dev_idx, int proto, int virtual_fd, int sd, int fid, int p
> void *nla_start_poll_data[2] = {&dev_idx, &proto};
> int nla_start_poll_len[2] = {4, 4};
> pthread_t thread_t;
> - int status;
> + intptr_t status;
> int rc;
>
> rc = pthread_create(&thread_t, NULL, virtual_poll_start,
> @@ -605,7 +606,7 @@ int start_polling(int dev_idx, int proto, int virtual_fd, int sd, int fid, int p
> int stop_polling(int dev_idx, int virtual_fd, int sd, int fid, int pid)
> {
> pthread_t thread_t;
> - int status;
> + intptr_t status;
> int rc;
>
> rc = pthread_create(&thread_t, NULL, virtual_poll_stop,
> @@ -816,7 +817,7 @@ int disconnect_tag(int nfc_sock, int virtual_fd)
> {
> pthread_t thread_t;
> char buf[256];
> - int status;
> + intptr_t status;
> int len;
>
> send(nfc_sock, &nci_t4t_select_cmd3[3], sizeof(nci_t4t_select_cmd3) - 3, 0);
> @@ -860,7 +861,7 @@ TEST_F(NCI, deinit)
> {
> struct msgtemplate msg;
> pthread_t thread_t;
> - int status;
> + intptr_t status;
> int rc;
>
> rc = get_nci_devid(self->sd, self->fid, self->pid, self->dev_idex,
Friendly ping!
Thomas
next prev parent reply other threads:[~2026-08-13 14:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 11:23 Thomas Huth
2026-07-21 20:56 ` Jakub Kicinski
2026-08-13 14:45 ` Thomas Huth [this message]
2026-08-17 17:30 ` David Heidelberg
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=68b1d486-37a9-43d4-a02f-66fa4689d437@redhat.com \
--to=thuth@redhat.com \
--cc=bongsu.jeon@samsung.com \
--cc=david@ixit.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=oe-linux-nfc@lists.linux.dev \
--cc=shuah@kernel.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
all inboxes | Powered by JetHome®