Re: [PATCH] selftests/exec: Use %zu to format size_t
From: David Drysdale
Date: Fri Jan 02 2015 - 08:46:40 EST
On Mon, Dec 22, 2014 at 6:14 PM, Shuah Khan <shuahkh@xxxxxxxxxxxxxxx> wrote:
>
> On 12/21/2014 03:58 AM, Geert Uytterhoeven wrote:
> > On 32-bit:
> >
> > execveat.c: In function 'check_execveat_pathmax':
> > execveat.c:183: warning: format '%lu' expects type 'long unsigned int', but argument 3 has type 'size_t'
> > execveat.c:187: warning: format '%lu' expects type 'long unsigned int', but argument 2 has type 'size_t'
> >
> > Signed-off-by: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
> > ---
> > tools/testing/selftests/exec/execveat.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/tools/testing/selftests/exec/execveat.c b/tools/testing/selftests/exec/execveat.c
> > index 33a5c06d95caa038..d273624c93a64254 100644
> > --- a/tools/testing/selftests/exec/execveat.c
> > +++ b/tools/testing/selftests/exec/execveat.c
> > @@ -179,11 +179,11 @@ static int check_execveat_pathmax(int dot_dfd, const char *src, int is_script)
> > */
> > fd = open(longpath, O_RDONLY);
> > if (fd > 0) {
> > - printf("Invoke copy of '%s' via filename of length %lu:\n",
> > + printf("Invoke copy of '%s' via filename of length %zu:\n",
> > src, strlen(longpath));
> > fail += check_execveat(fd, "", AT_EMPTY_PATH);
> > } else {
> > - printf("Failed to open length %lu filename, errno=%d (%s)\n",
> > + printf("Failed to open length %zu filename, errno=%d (%s)\n",
> > strlen(longpath), errno, strerror(errno));
> > fail++;
> > }
> >
>
>
> Applied to kernel/git/shuah/linux-kselftest.git fixes
> for 3.19-rc2
>
> thanks,
> -- Shuah
Thanks for fixing, and apologies for the delay in responding.
Acked-by: David Drysdale <drysdale@xxxxxxxxxx>
> --
> Shuah Khan
> Sr. Linux Kernel Developer
> Open Source Innovation Group
> Samsung Research America (Silicon Valley)
> shuahkh@xxxxxxxxxxxxxxx | (970) 217-8978
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/