From: Steve Dickson <steved@redhat.com>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>,
linux-nfs@vger.kernel.org
Subject: Re: [PATCH v2 3/3] support/backend_sqlite.c: fix getrandom() fallback
Date: Fri, 15 May 2026 08:52:18 -0400 [thread overview]
Message-ID: <3351afd6-13d4-4ee0-a5ba-08b6591db437@redhat.com> (raw)
In-Reply-To: <20260408173535.3992116-3-giulio.benetti@benettiengineering.com>
On 4/8/26 1:35 PM, Giulio Benetti wrote:
> In old Linux/Glibc versions __NR_getrandom is defined in <sys/random.h>
> so let's add it to fix build failure.
>
> Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
Committed (tag: nfs-utils-2-9-2-rc3)
steved
> ---
> V1->V2
> * added patch
> ---
> support/reexport/backend_sqlite.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/support/reexport/backend_sqlite.c b/support/reexport/backend_sqlite.c
> index 0eb5ea37..a1e981e4 100644
> --- a/support/reexport/backend_sqlite.c
> +++ b/support/reexport/backend_sqlite.c
> @@ -9,6 +9,8 @@
> #include <string.h>
> #include <unistd.h>
>
> +#include <sys/syscall.h>
> +
> #ifdef HAVE_GETRANDOM
> # include <sys/random.h>
> # if !defined(SYS_getrandom) && defined(__NR_getrandom)
next prev parent reply other threads:[~2026-05-15 12:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 17:35 [PATCH v2 1/3] fh_key_file: fix missing string.h inclusion Giulio Benetti
2026-04-08 17:35 ` [PATCH v2 2/3] Introduce compat.h file to deal with old Linux api and fix build failure due to missing NETLINK_EXT_ACK Giulio Benetti
2026-05-15 12:52 ` Steve Dickson
2026-04-08 17:35 ` [PATCH v2 3/3] support/backend_sqlite.c: fix getrandom() fallback Giulio Benetti
2026-05-15 12:52 ` Steve Dickson [this message]
2026-05-15 12:52 ` [PATCH v2 1/3] fh_key_file: fix missing string.h inclusion Steve Dickson
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=3351afd6-13d4-4ee0-a5ba-08b6591db437@redhat.com \
--to=steved@redhat.com \
--cc=giulio.benetti@benettiengineering.com \
--cc=linux-nfs@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.