All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Lai Jiangshan <jiangshanlai@gmail.com>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
	Lai Jiangshan <laijs@linux.alibaba.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH 2/3] x86/hw_breakpoint: Add stack_canary to hw_breakpoints denylist
Date: Mon, 13 Dec 2021 20:57:32 +0100	[thread overview]
Message-ID: <20211213195732.GA16608@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <20211213042215.3096-3-jiangshanlai@gmail.com>

On Mon, Dec 13, 2021 at 12:22:14PM +0800, Lai Jiangshan wrote:
> From: Lai Jiangshan <laijs@linux.alibaba.com>
> 
> When stack-protector is enabled, entry functions may access
> to the stack_canary.
> 
> Signed-off-by: Lai Jiangshan <laijs@linux.alibaba.com>
> ---
>  arch/x86/kernel/hw_breakpoint.c | 8 ++++++++
>  1 file changed, 8 insertions(+)
> 
> diff --git a/arch/x86/kernel/hw_breakpoint.c b/arch/x86/kernel/hw_breakpoint.c
> index 668a4a6533d9..b2b64afdf9c0 100644
> --- a/arch/x86/kernel/hw_breakpoint.c
> +++ b/arch/x86/kernel/hw_breakpoint.c
> @@ -315,6 +315,14 @@ static inline bool within_cpu_entry(unsigned long addr, unsigned long end)
>  		if (within_area(addr, end, (unsigned long)&per_cpu(cpu_dr7, cpu),
>  				sizeof(cpu_dr7)))
>  			return true;
> +
> +		/*
> +		 * When stack-protector is enabled, entry functions may access
> +		 * to the stack_canary.
> +		 */
> +		if (within_area(addr, end, (unsigned long)&per_cpu(fixed_percpu_data, cpu),
> +				sizeof(struct fixed_percpu_data)))
> +			return true;

Isn't fixed_percpu_data x86_64 only?

>  	}
>  
>  	return false;

  reply	other threads:[~2021-12-13 19:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-13  4:22 [PATCH 0/3] x86/entry: Fix 3 suspicious bugs Lai Jiangshan
2021-12-13  4:22 ` [PATCH 1/3] X86/db: Change __this_cpu_read() to this_cpu_read() in hw_breakpoint_active() Lai Jiangshan
2021-12-13 19:09   ` Borislav Petkov
2021-12-14  2:51     ` Lai Jiangshan
2021-12-14  9:33       ` Borislav Petkov
2021-12-13 19:46   ` Peter Zijlstra
2021-12-13  4:22 ` [PATCH 2/3] x86/hw_breakpoint: Add stack_canary to hw_breakpoints denylist Lai Jiangshan
2021-12-13 19:57   ` Peter Zijlstra [this message]
2021-12-13  4:22 ` [PATCH 3/3] x86/sev: The code for returning to user space is also in syscall gap Lai Jiangshan
2021-12-14 21:51   ` Borislav Petkov
2021-12-17 10:05     ` Joerg Roedel
2021-12-17 10:30       ` Borislav Petkov
2021-12-17 11:00         ` Joerg Roedel
2022-01-18 10:32           ` Borislav Petkov
2022-01-18 15:37             ` Lai Jiangshan
2022-04-12 13:00     ` Lai Jiangshan

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=20211213195732.GA16608@worktop.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=jiangshanlai@gmail.com \
    --cc=laijs@linux.alibaba.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@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.