[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2023052824-dagger-retread-2325@gregkh>
Date: Sun, 28 May 2023 08:42:34 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: Hardik Garg <hargar@...ux.microsoft.com>
Cc: stable@...r.kernel.org, shuah@...nel.org, jeffxu@...gle.com,
linux-kselftest@...r.kernel.org, linux-kernel@...r.kernel.org,
code@...icks.com, niyelchu@...ux.microsoft.com
Subject: Re: [PATCH 6.1 5.15 5.10 5.4 4.19 4.14] selftests/memfd: Fix unknown
type name build failure
On Fri, May 26, 2023 at 04:21:36PM -0700, Hardik Garg wrote:
> Partially backport v6.3 commit 11f75a01448f ("selftests/memfd: add
> tests for MFD_NOEXEC_SEAL MFD_EXEC") to fix an unknown type name
> build error.
> In some systems, the __u64 typedef is not present due to differences
> in system headers, causing compilation errors like this one:
>
> fuse_test.c:64:8: error: unknown type name '__u64'
> 64 | static __u64 mfd_assert_get_seals(int fd)
>
> This header includes the __u64 typedef which increases the
> likelihood of successful compilation on a wider variety of systems.
>
> Signed-off-by: Hardik Garg <hargar@...ux.microsoft.com>
> ---
> tools/testing/selftests/memfd/fuse_test.c | 1 +
> 1 file changed, 1 insertion(+)
Now queued up, thanks.
greg k-h
Powered by blists - more mailing lists