From: Sam Ravnborg <sam@ravnborg.org>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: sparclinux@vger.kernel.org
Subject: Re: [PATCH] sparc32: fix a braino in fault handling in csum_and_copy_..._user()
Date: Fri, 27 Oct 2023 22:14:47 +0200 [thread overview]
Message-ID: <20231027201447.GA5545@ravnborg.org> (raw)
In-Reply-To: <20231027190220.GL800259@ZenIV>
Hi Al,
>
> Looking at the csum_and_copy_... instances on various architectures,
> noticing that and going "how the fuck could it possibly work and
> what moron had broken it? Oh, lovely - it couldn't, it doesn't
> and that moron had been myself ;-/"
:-)
>
> > Do you actually use sparc32 these
> > days?
>
> qemu image only, TBH - I have an SS20 box, but it hadn't booted for
> about 10 years...
Looked at my "museum". At least 5 pcs of sparc32 boxes but I guess
the NVRAM needs repair on all of them.
I have a LEON4 board somewhere on the shelf too.
None of this powered up for years either - but I cannot make myself
getting rid of it. Because maybe one day I find time...
All that said - I have also once suggested to drop sun4m support,
keeping only the LEON parts. Back then there was some resistance,
but all for sentimental reasons and I can relate to that, since
I kept the sparc32 boxes around.
> > You could also kill the EX2 define while touchign the file,
> > it is no longer used after ab5e8b331244.
>
> Er? No EX2 in checksum_32.S... There is one in copy_user.S,
> but that one _is_ used -
>
> copy_user_table_end:
> be copy_user_last7
> andcc %g1, 4, %g0
>
> EX(ldd [%o1], %g2, and %g1, 0xf)
> add %o0, 8, %o0
> add %o1, 8, %o1
> EX(st %g2, [%o0 - 0x08], and %g1, 0xf)
> EX2(st %g3, [%o0 - 0x04], and %g1, 0xf, %g1, sub %g1, 4)
Yeah, I'm blind. Somehow the grep output tricked me.
Sam
prev parent reply other threads:[~2023-10-27 20:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 2:16 [PATCH] sparc32: fix a braino in fault handling in csum_and_copy_..._user() Al Viro
2023-10-27 18:47 ` Sam Ravnborg
2023-10-27 19:02 ` Al Viro
2023-10-27 20:14 ` Sam Ravnborg [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=20231027201447.GA5545@ravnborg.org \
--to=sam@ravnborg.org \
--cc=sparclinux@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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.