From: Peter Zijlstra <peterz@infradead.org>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: READ_ONCE() + STACKPROTECTOR_STRONG == :/
Date: Thu, 12 Dec 2019 22:09:49 +0100 [thread overview]
Message-ID: <20191212210949.GE11457@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <20191212210052.GA8906@avx2>
On Fri, Dec 13, 2019 at 12:00:52AM +0300, Alexey Dobriyan wrote:
> > We could move the kernel to C++ and write:
> >
> > std::remove_volatile<typeof(p)>::type __p = (p);
> >
> > /me runs like hell...
>
> Did you just said I can send "struct sched_domain::private" and
> "struct wait_queue_entry::private" rename?
> :^)
I don't believe those are the only usage of C++ keywords. IIRC I'm using
'class' somewhere as well.
> Doable but not until C++20. constinit and designated initializers are
> pretty mandatory.
>
> Debian GNU/Linux 8 debian88 ttyS0
>
> debian88 login: root
> Password:
> Last login: Thu Sep 19 01:04:29 +03 2019 on tty1
> Linux debian88 5.3.0+ #1 SMP PREEMPT Thu Sep 19 01:02:26 +03 2019 x86_64
> root@debian88:~# cat /proc/$(pgrep sshd)/stack
> [<0>] _ZL9do_selectiP11fd_set_bitsP10timespec64+0x5ac/0x750
> [<0>] _Z15core_sys_selectiP15__kernel_fd_setS0_S0_P10timespec64+0x143/0x260
Argh.. I forgot how I hated mangled names.
> [<0>] __x64_sys_select+0xa7/0xf0
> [<0>] do_syscall_64+0x3b/0xe7
> [<0>] entry_SYSCALL_64_after_hwframe+0x44/0xa9
prev parent reply other threads:[~2019-12-12 21:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 21:00 READ_ONCE() + STACKPROTECTOR_STRONG == :/ Alexey Dobriyan
2019-12-12 21:09 ` Peter Zijlstra [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=20191212210949.GE11457@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=adobriyan@gmail.com \
--cc=linux-kernel@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