All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Garnier <thgarnie@google.com>
To: Jiri Kosina <jikos@kernel.org>
Cc: "Rafael J . Wysocki" <rjw@rjwysocki.net>,
	Len Brown <len.brown@intel.com>, Pavel Machek <pavel@ucw.cz>,
	Linux PM list <linux-pm@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Kees Cook <keescook@chromium.org>,
	Kernel Hardening <kernel-hardening@lists.openwall.com>,
	Borislav Petkov <bpetkov@suse.de>,
	Yinghai Lu <yinghai@kernel.org>
Subject: Re: [PATCH v1] x86/power/64: Restore processor state before using per-cpu variables
Date: Fri, 12 Aug 2016 09:03:05 -0700	[thread overview]
Message-ID: <CAJcbSZHG3ULCATigD0hhzOEXWi+GiDhtiBQdgaTiYnkP3k2fHw@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1608121044120.22028@cbobk.fhfr.pm>

On Fri, Aug 12, 2016 at 2:23 AM, Jiri Kosina <jikos@kernel.org> wrote:
> On Fri, 12 Aug 2016, Jiri Kosina wrote:
>
> That's pretty nasty, as turning LOCKDEP on has sideffects on the code
> that'd normally not be expected to be run at all (tracepoint off).
>
> Oh well.

Thanks for the analysis, I didn't got that far so I had no idea how
everything was connected.

> Thanks again,

Thanks you and Borislav for finding it.

WARNING: multiple messages have this Message-ID (diff)
From: Thomas Garnier <thgarnie@google.com>
To: Jiri Kosina <jikos@kernel.org>
Cc: "Rafael J . Wysocki" <rjw@rjwysocki.net>,
	Len Brown <len.brown@intel.com>, Pavel Machek <pavel@ucw.cz>,
	Linux PM list <linux-pm@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Kees Cook <keescook@chromium.org>,
	Kernel Hardening <kernel-hardening@lists.openwall.com>,
	Borislav Petkov <bpetkov@suse.de>,
	Yinghai Lu <yinghai@kernel.org>
Subject: [kernel-hardening] Re: [PATCH v1] x86/power/64: Restore processor state before using per-cpu variables
Date: Fri, 12 Aug 2016 09:03:05 -0700	[thread overview]
Message-ID: <CAJcbSZHG3ULCATigD0hhzOEXWi+GiDhtiBQdgaTiYnkP3k2fHw@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1608121044120.22028@cbobk.fhfr.pm>

On Fri, Aug 12, 2016 at 2:23 AM, Jiri Kosina <jikos@kernel.org> wrote:
> On Fri, 12 Aug 2016, Jiri Kosina wrote:
>
> That's pretty nasty, as turning LOCKDEP on has sideffects on the code
> that'd normally not be expected to be run at all (tracepoint off).
>
> Oh well.

Thanks for the analysis, I didn't got that far so I had no idea how
everything was connected.

> Thanks again,

Thanks you and Borislav for finding it.

  reply	other threads:[~2016-08-12 16:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-11 21:49 [PATCH v1] x86/power/64: Restore processor state before using per-cpu variables Thomas Garnier
2016-08-11 21:49 ` [kernel-hardening] " Thomas Garnier
2016-08-12  5:49 ` Borislav Petkov
2016-08-12  5:49   ` [kernel-hardening] " Borislav Petkov
2016-08-12 11:14   ` Rafael J. Wysocki
2016-08-12 11:14     ` [kernel-hardening] " Rafael J. Wysocki
2016-08-12 16:03     ` Thomas Garnier
2016-08-12 16:03       ` [kernel-hardening] " Thomas Garnier
2016-08-12 17:45       ` Borislav Petkov
2016-08-12 17:45         ` [kernel-hardening] " Borislav Petkov
2016-08-12  6:01 ` Jiri Kosina
2016-08-12  6:01   ` [kernel-hardening] " Jiri Kosina
2016-08-12  9:23   ` Jiri Kosina
2016-08-12  9:23     ` [kernel-hardening] " Jiri Kosina
2016-08-12 16:03     ` Thomas Garnier [this message]
2016-08-12 16:03       ` Thomas Garnier
2016-08-12  6:29 ` Pavel Machek
2016-08-12  6:29   ` [kernel-hardening] " Pavel Machek

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=CAJcbSZHG3ULCATigD0hhzOEXWi+GiDhtiBQdgaTiYnkP3k2fHw@mail.gmail.com \
    --to=thgarnie@google.com \
    --cc=bpetkov@suse.de \
    --cc=jikos@kernel.org \
    --cc=keescook@chromium.org \
    --cc=kernel-hardening@lists.openwall.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=rjw@rjwysocki.net \
    --cc=yinghai@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 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.