From: Andreas Schwab <schwab@linux-m68k.org>
To: Michael Schmitz <schmitzmic@gmail.com>
Cc: Chuck Lever III <chuck.lever@oracle.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Chuck Lever <cel@kernel.org>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
David Howells <dhowells@redhat.com>,
"simo@redhat.com" <simo@redhat.com>,
"linux-kselftest@vger.kernel.org"
<linux-kselftest@vger.kernel.org>,
"linux-m68k@lists.linux-m68k.org"
<linux-m68k@lists.linux-m68k.org>
Subject: Re: [PATCH v2 00/41] RPCSEC GSS krb5 enhancements
Date: Thu, 23 Feb 2023 22:46:24 +0100 [thread overview]
Message-ID: <87cz60dphr.fsf@igel.home> (raw)
In-Reply-To: <4697cebe-5399-17f6-4580-99f3f3c86db6@gmail.com> (Michael Schmitz's message of "Fri, 24 Feb 2023 07:19:28 +1300")
On Feb 24 2023, Michael Schmitz wrote:
> Hi Andreas,
>
> On 24/02/23 06:57, Andreas Schwab wrote:
>> On Feb 23 2023, Chuck Lever III wrote:
>>
>>> Assuming that "PC:" on m68k is the same as "RIP:" on x86...
>>> this does not make sense. rfc6803_suite is not a function.
>> That can mean that something has overwritten the return PC.
>>
> Wouldn't you expect a format error in that case?
What format error do you mean? There was a chk exception, presumably
because the first word of rfc6803_suite happens to match the encoding of
the chk insn.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2023-02-23 21:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <167380196429.10651.4103075913257868035.stgit@bazille.1015granger.net>
2023-02-23 13:05 ` [PATCH v2 00/41] RPCSEC GSS krb5 enhancements Geert Uytterhoeven
2023-02-23 14:00 ` Chuck Lever III
2023-02-23 15:16 ` Geert Uytterhoeven
2023-02-23 16:18 ` Chuck Lever III
2023-02-23 16:52 ` Geert Uytterhoeven
2023-02-23 19:32 ` Chuck Lever III
2023-02-27 9:51 ` Geert Uytterhoeven
2023-02-27 15:06 ` Chuck Lever III
2023-02-27 15:37 ` Geert Uytterhoeven
2023-02-23 17:57 ` Andreas Schwab
2023-02-23 18:19 ` Michael Schmitz
2023-02-23 21:46 ` Andreas Schwab [this message]
2023-02-23 22:17 ` Michael Schmitz
2023-02-23 18:28 ` Eero Tamminen
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=87cz60dphr.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=dhowells@redhat.com \
--cc=geert@linux-m68k.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-nfs@vger.kernel.org \
--cc=schmitzmic@gmail.com \
--cc=simo@redhat.com \
/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).