From: Tom de Vries <tdevries@suse.de>
To: Borislav Petkov <bp@alien8.de>, Peter Zijlstra <peterz@infradead.org>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
andrew.cooper3@citrix.com,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: [PATCH v2] x86/debug: Fix DR6 handling
Date: Fri, 29 Jan 2021 17:59:54 +0100 [thread overview]
Message-ID: <50670b90-6d53-8c65-b3c8-e76fc9e2a1d3@suse.de> (raw)
In-Reply-To: <20210129144816.GB27841@zn.tnic>
On 1/29/21 3:48 PM, Borislav Petkov wrote:
> On Thu, Jan 28, 2021 at 10:16:27PM +0100, Peter Zijlstra wrote:
>>
>> Tom reported that one of the GDB test-cases failed, and Boris bisected
>> it to commit:
>>
>> d53d9bc0cf78 ("x86/debug: Change thread.debugreg6 to thread.virtual_dr6")
>>
>> The debugging session led us to commit:
>>
>> 6c0aca288e72 ("x86: Ignore trap bits on single step exceptions")
>>
>> It turns out that TF and data breakpoints are both traps and will be
>> merged, while instruction breakpoints are faults and will not be
>> merged. This means 6c0aca288e72 is wrong, we only need to exclude TF
>> and instruction breakpoints while we can merge TF and data
>> breakpoints.
>>
>> Fixes: d53d9bc0cf78 ("x86/debug: Change thread.debugreg6 to thread.virtual_dr6")
>> Fixes: 6c0aca288e72 ("x86: Ignore trap bits on single step exceptions")
>> Reported-by: Tom de Vries <tdevries@suse.de>
>> Bisected-by: Borislav Petkov <bp@alien8.de>
>> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
>
> I guess
>
> Cc: <stable@vger.kernel.org>
>
> Also,
>
> Reviewed-by: Borislav Petkov <bp@suse.de>
>
> And gdb testsuite is a bit happier:
>
> --- before
> +++ after
> === gdb Summary ===
>
> -# of expected passes 70822
> -# of unexpected failures 899
> +# of expected passes 70852
> +# of unexpected failures 869
> # of expected failures 74
> # of known failures 99
> # of untested testcases 114
>
> You just fixed 30(!) testcases.
>
> :-)
>
Hi Boris,
thanks for testing this, and just to confirm: the total number of
regressions I see in the gdb testsuite related to watchpoints is indeed 30.
Thanks,
- Tom
prev parent reply other threads:[~2021-01-29 17:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 18:20 [PATCH] x86/debug: 'Fix' ptrace dr6 output Peter Zijlstra
2021-01-28 18:45 ` Andrew Cooper
2021-01-28 20:21 ` Tom de Vries
2021-01-28 21:16 ` [PATCH v2] x86/debug: Fix DR6 handling Peter Zijlstra
2021-01-28 23:28 ` [PATCH] selftests: breakpoints: Add "WINE" test for x86 Thomas Gleixner
[not found] ` <YBPQq6ccKL68aIZg@hirez.programming.kicks-ass.net>
2021-01-29 19:09 ` Thomas Gleixner
[not found] ` <20210129154109.GA1391@redhat.com>
2021-01-29 16:27 ` [PATCH v2] x86/debug: Fix DR6 handling Borislav Petkov
[not found] ` <20210129144816.GB27841@zn.tnic>
2021-01-29 16:59 ` Tom de Vries [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=50670b90-6d53-8c65-b3c8-e76fc9e2a1d3@suse.de \
--to=tdevries@suse.de \
--cc=andrew.cooper3@citrix.com \
--cc=bp@alien8.de \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®