From: Al Viro <viro@ZenIV.linux.org.uk>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Jakub Jelinek <jakub@redhat.com>,
Vineet Gupta <Vineet.Gupta1@synopsys.com>,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH] ARC: uaccess: get_user to zero out dest in cause of fault
Date: Sun, 21 Aug 2016 02:40:30 +0100 [thread overview]
Message-ID: <20160821014020.GW2356@ZenIV.linux.org.uk> (raw)
In-Reply-To: <DEDD7B96-A44C-4992-A1C3-067D607EB419@zytor.com>
On Sat, Aug 20, 2016 at 06:09:15PM -0700, H. Peter Anvin wrote:
> >Sorry for the bogus noise. I don't know why I was so convinced setjmp
> >needed special gcc semantics.
> >
> > Linus
>
> I think the specific name setjmp() is magic in gcc.
It is; attribute equivalent is returns_twice. I wonder if "explicitly
clobber everything if we got false" + asm volatile to prevent reordering
would suffice for our purposes, but that's really a question for gcc
folks...
next prev parent reply other threads:[~2016-08-21 1:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-19 19:10 [PATCH] ARC: uaccess: get_user to zero out dest in cause of fault Vineet Gupta
2016-08-19 19:10 ` Vineet Gupta
2016-08-19 21:24 ` Al Viro
2016-08-19 22:00 ` Linus Torvalds
2016-08-19 22:11 ` Linus Torvalds
2016-08-20 23:32 ` Linus Torvalds
2016-08-21 0:11 ` Al Viro
2016-08-21 0:45 ` Linus Torvalds
2016-08-21 1:00 ` Linus Torvalds
2016-08-21 1:09 ` H. Peter Anvin
2016-08-21 1:40 ` Al Viro [this message]
2016-08-21 4:54 ` Jakub Jelinek
2016-08-21 6:42 ` Al Viro
2016-08-21 17:52 ` Linus Torvalds
2016-08-22 22:23 ` Linus Torvalds
2016-08-22 23:12 ` H. Peter Anvin
2016-08-22 23:48 ` Linus Torvalds
2016-08-22 23:51 ` H. Peter Anvin
2016-08-22 23:57 ` David Miller
2016-08-23 0:09 ` H. Peter Anvin
2016-08-23 0:17 ` Al Viro
2016-08-22 23:19 ` H. Peter Anvin
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=20160821014020.GW2356@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=Vineet.Gupta1@synopsys.com \
--cc=hpa@zytor.com \
--cc=jakub@redhat.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=torvalds@linux-foundation.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.