From: Peter Zijlstra <peterz@infradead.org>
To: Kyle Huey <me@kylehuey.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Alexandre Chartre <alexandre.chartre@oracle.com>,
Andy Lutomirski <luto@kernel.org>,
Robert O'Callahan <rocallahan@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<x86@kernel.org>, "Paul E. McKenney" <paulmck@kernel.org>,
Frederic Weisbecker <frederic@kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Sean Christopherson <sean.j.christopherson@intel.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
Petr Mladek <pmladek@suse.com>,
Steven Rostedt <rostedt@goodmis.org>,
Joel Fernandes <joel@joelfernandes.org>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Juergen Gross <jgross@suse.com>, Brian Gerst <brgerst@gmail.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Will Deacon <will@kernel.org>
Subject: Re: [REGRESSION 5.8] x86/entry: DR0 break-on-write not working
Date: Wed, 19 Aug 2020 23:35:34 +0200 [thread overview]
Message-ID: <20200819213534.GQ3982@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <CAP045ApfQnsHsimmhLsSeL2OSB98-Q3f=nM4em5rqr_paz4=5Q@mail.gmail.com>
On Wed, Aug 19, 2020 at 12:28:16PM -0700, Kyle Huey wrote:
> > I'm guess that is not the expected outcome, is that the same failure you
> > saw?
>
> Yes. Is status also 0x4d00 for you?
Indeed.
> The program is expected to complete with no assertions firing.
When I comment out the break-on-exec test, the break-on-write test
succeeds.
When I add a few printk()'s to our #DB handler (6) the program will
magically work again.
I'm not much for ptrace(), but are we sure the test program is well
behaved?
The below also always works..
---
/* -*- Mode: C; tab-width: 8; c-basic-offset: 2; indent-tabs-mode: nil; -*- */
#include <stdio.h>
#include <unistd.h>
#include <sys/types.h>
#include <sys/ptrace.h>
#include <stdarg.h>
#include <assert.h>
#include <sys/wait.h>
#include <errno.h>
#include <string.h>
#include <stddef.h>
#include <sys/user.h>
/**
* Print the printf-like arguments to stdout as atomic-ly as we can
* manage. Async-signal-safe. Does not flush stdio buffers (doing so
* isn't signal safe).
*/
__attribute__((format(printf, 1, 2))) inline static int atomic_printf(
const char* fmt, ...) {
va_list args;
char buf[1024];
int len;
va_start(args, fmt);
len = vsnprintf(buf, sizeof(buf) - 1, fmt, args);
va_end(args);
return write(STDOUT_FILENO, buf, len);
}
/**
* Write |str| on its own line to stdout as atomic-ly as we can
* manage. Async-signal-safe. Does not flush stdio buffers (doing so
* isn't signal safe).
*/
inline static int atomic_puts(const char* str) {
return atomic_printf("%s\n", str);
}
inline static int check_cond(int cond) {
if (!cond) {
atomic_printf("FAILED: errno=%d (%s)\n", errno, strerror(errno));
}
return cond;
}
#define test_assert(cond) assert("FAILED: !" && check_cond(cond))
#define NEW_VALUE 0xabcdef
static void breakpoint(void) {}
static char watch_var;
int main(void) {
pid_t child;
int status;
int pipe_fds[2];
test_assert(0 == pipe(pipe_fds));
if (0 == (child = fork())) {
char ch;
read(pipe_fds[0], &ch, 1);
breakpoint();
watch_var = 1;
return 77;
}
test_assert(0 == ptrace(PTRACE_ATTACH, child, NULL, NULL));
test_assert(child == waitpid(child, &status, 0));
test_assert(status == ((SIGSTOP << 8) | 0x7f));
test_assert(1 == write(pipe_fds[1], "x", 1));
test_assert(0 == ptrace(PTRACE_POKEUSER, child,
(void*)offsetof(struct user, u_debugreg[0]),
(void*)breakpoint));
test_assert(0 == ptrace(PTRACE_POKEUSER, child,
(void*)offsetof(struct user, u_debugreg[1]),
&watch_var));
test_assert(0 == ptrace(PTRACE_POKEUSER, child,
(void*)offsetof(struct user, u_debugreg[7]),
(void*)0x100005));
test_assert(0 == ptrace(PTRACE_CONT, child, NULL, NULL));
test_assert(child == waitpid(child, &status, 0));
test_assert(status == ((SIGTRAP << 8) | 0x7f));
test_assert(0x1 == ptrace(PTRACE_PEEKUSER, child,
(void*)offsetof(struct user, u_debugreg[6])));
test_assert(0 == ptrace(PTRACE_CONT, child, NULL, NULL));
test_assert(child == waitpid(child, &status, 0));
test_assert(status == ((SIGTRAP << 8) | 0x7f));
test_assert(0x2 == ptrace(PTRACE_PEEKUSER, child,
(void*)offsetof(struct user, u_debugreg[6])));
test_assert(0 == ptrace(PTRACE_DETACH, child, NULL, NULL));
test_assert(child == waitpid(child, &status, 0));
test_assert(WIFEXITED(status));
test_assert(WEXITSTATUS(status) == 77);
atomic_puts("EXIT-SUCCESS");
return 0;
}
next prev parent reply other threads:[~2020-08-19 21:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 17:53 [REGRESSION 5.8] x86/entry: DR0 break-on-write not working Kyle Huey
2020-08-19 18:41 ` peterz
2020-08-19 19:28 ` Kyle Huey
2020-08-19 21:35 ` Peter Zijlstra [this message]
2020-08-19 22:47 ` Josh Poimboeuf
2020-08-20 0:14 ` Andy Lutomirski
2020-08-20 3:46 ` Josh Poimboeuf
2020-08-20 8:35 ` peterz
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=20200819213534.GQ3982@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=alexandre.chartre@oracle.com \
--cc=boris.ostrovsky@oracle.com \
--cc=brgerst@gmail.com \
--cc=frederic@kernel.org \
--cc=jgross@suse.com \
--cc=joel@joelfernandes.org \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=me@kylehuey.com \
--cc=mhiramat@kernel.org \
--cc=paulmck@kernel.org \
--cc=pbonzini@redhat.com \
--cc=pmladek@suse.com \
--cc=rocallahan@gmail.com \
--cc=rostedt@goodmis.org \
--cc=sean.j.christopherson@intel.com \
--cc=tglx@linutronix.de \
--cc=will@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox