linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>
Cc: Ard Biesheuvel <ardb@kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	Keith Packard <keithpac@amazon.com>,
	Arnd Bergmann <arnd@arndb.de>,
	Amit Daniel Kachhap <amit.kachhap@arm.com>,
	Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [GIT PULL] ARM: support THREAD_INFO_IN_TASK
Date: Thu, 14 Oct 2021 09:24:53 -0700	[thread overview]
Message-ID: <202110140924.CDCEB90@keescook> (raw)
In-Reply-To: <YWhRDk3Z10j99sRe@shell.armlinux.org.uk>

On Thu, Oct 14, 2021 at 04:47:26PM +0100, Russell King (Oracle) wrote:
> On Sun, Oct 10, 2021 at 09:50:52AM +0200, Ard Biesheuvel wrote:
> > On Mon, 27 Sept 2021 at 17:06, Ard Biesheuvel <ardb@kernel.org> wrote:
> > >
> > > The following changes since commit 6880fa6c56601bb8ed59df6c30fd390cc5f6dd8f:
> > >
> > >   Linux 5.15-rc1 (2021-09-12 16:28:37 -0700)
> > >
> > > are available in the Git repository at:
> > >
> > >   git://git.kernel.org/pub/scm/linux/kernel/git/ardb/linux.git tags/pr-arm32-ti-in-task
> > >
> > > for you to fetch changes up to 18ed1c01a7dd3d7c780b06a49124da237a4c1790:
> > >
> > >   ARM: smp: Enable THREAD_INFO_IN_TASK (2021-09-27 16:54:02 +0200)
> > >
> > > ----------------------------------------------------------------
> > > ARM: support THREAD_INFO_IN_TASK
> > >
> > > Move thread_info off the stack and into the task struct, as is done by
> > > many other architectures. This requires a method to find the task struct
> > > of the task currently running on the CPU, which is provided in this case
> > > by the user space TLS (Thread Local Storage) register. This implies that
> > > the feature is only supported on CPUs that implement this register,
> > > i.e., ARM v6k or later.
> > >
> > > Kindly tested by Amit and reviewed by Linus. The first patch is against
> > > the GCC plugins subsystem, but was reviewed by the maintainer and can be
> > > taken through the ARM tree.
> > >
> > > ----------------------------------------------------------------
> > >
> > 
> > Ping?
> 
> I haven't forgotten about it, I just haven't really opened my tree for
> new material yet... which I need to do this week, if I have time after
> catching up.

Thanks! Getting this into -next would help with the irq series and vmap
stack series too.

-- 
Kees Cook

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2021-10-14 16:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-27 15:04 [GIT PULL] ARM: support THREAD_INFO_IN_TASK Ard Biesheuvel
2021-10-10  7:50 ` Ard Biesheuvel
2021-10-11 17:22   ` Kees Cook
2021-10-14 15:47   ` Russell King (Oracle)
2021-10-14 16:24     ` Kees Cook [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=202110140924.CDCEB90@keescook \
    --to=keescook@chromium.org \
    --cc=amit.kachhap@arm.com \
    --cc=ardb@kernel.org \
    --cc=arnd@arndb.de \
    --cc=keithpac@amazon.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux@armlinux.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 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).