linux-m68k.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Chuck Lever <cel@kernel.org>
Cc: linux-nfs@vger.kernel.org, linux-kselftest@vger.kernel.org,
	linux-m68k@lists.linux-m68k.org
Subject: Re: [PATCH] SUNRPC: Ensure test case arrays are properly terminated
Date: Mon, 27 Feb 2023 20:43:23 +0100	[thread overview]
Message-ID: <CAMuHMdW7mKmji6yyd2w+TrX0toyMN5r=hWvyxtM8D=qdBLcdww@mail.gmail.com> (raw)
In-Reply-To: <167751664019.187639.5290505948970809072.stgit@bazille.1015granger.net>

Hi Chuck,

On Mon, Feb 27, 2023 at 5:53 PM Chuck Lever <cel@kernel.org> wrote:
> From: Chuck Lever <chuck.lever@oracle.com>
>
> Geert Uytterhoeven reports:
>
> ...
>         ok 9 Encrypt 13 bytes with camellia256-cts-cmac
>         ok 10 Encrypt 30 bytes with camellia256-cts-cmac
>     # RFC 6803 encryption: pass:0 fail:0 skip:10 total:10
>     ok 3 RFC 6803 encryption # SKIP Encryption type is not available
> 8<--- cut here ---
> Unable to handle kernel paging request at virtual address 73657420 when execute
> [73657420] *pgd=00000000
> Internal error: Oops: 80000005 [#1] ARM
> CPU: 0 PID: 1 Comm: swapper Tainted: G                 N 6.2.0-rc7-00133-g373f26a81164-dirty #9
> Hardware name: Generic DT based system
> PC is at 0x73657420
> LR is at kunit_run_tests+0x3e0/0x5f4
>
> On x86 with GCC 12, the missing array terminators did not seem to
> matter. Other platforms appear to be more picky.

Doesn't gcc on x86 align all arrays to a 16-byte boundary, hence
adding zero-padding here?

>
> Reported-by: Geert Uytterhoeven <geert@linux-m68k.org>
> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>

Tested-by: Geert Uytterhoeven <geert@linux-m68k.org>

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

      reply	other threads:[~2023-02-27 19:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-27 16:52 [PATCH] SUNRPC: Ensure test case arrays are properly terminated Chuck Lever
2023-02-27 19:43 ` Geert Uytterhoeven [this message]

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='CAMuHMdW7mKmji6yyd2w+TrX0toyMN5r=hWvyxtM8D=qdBLcdww@mail.gmail.com' \
    --to=geert@linux-m68k.org \
    --cc=cel@kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --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 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).