All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 218339] kernel goes unresponsive if single-stepping over an instruction which writes to an address for which a hardware read/write watchpoint has been set
Date: Wed, 10 Jan 2024 12:38:08 +0000	[thread overview]
Message-ID: <bug-218339-28872-dvVdfUc8On@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218339-28872@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=218339

Yao Yuan (yaoyuan0329@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |yaoyuan0329@gmail.com

--- Comment #3 from Yao Yuan (yaoyuan0329@gmail.com) ---
Hi,

I tried on my side but can't reproducce it, logs below. Any steps I missed ?

(gdb) b *0x00007ffff7fe4048                                                     
Breakpoint 1 at 0x7ffff7fe4048: file ./elf/rtld.c, line 527.                    
(gdb) c                                                                         
Continuing.                                                                     

Breakpoint 1, 0x00007ffff7fe4048 in _dl_start (arg=0x7fffffffe510) at
./elf/rtld.c:527                                                                
527     in ./elf/rtld.c                                                         
(gdb) disassemble                                                               
Dump of assembler code for function _dl_start:                                  
   0x00007ffff7fe4030 <+0>:     endbr64                                         
   0x00007ffff7fe4034 <+4>:     push   %rbp                                     
   0x00007ffff7fe4035 <+5>:     mov    %rsp,%rbp                                
   0x00007ffff7fe4038 <+8>:     push   %r15                                     
   0x00007ffff7fe403a <+10>:    push   %r14                                     
   0x00007ffff7fe403c <+12>:    push   %r13                                     
   0x00007ffff7fe403e <+14>:    push   %r12                                     
   0x00007ffff7fe4040 <+16>:    push   %rbx                                     
   0x00007ffff7fe4041 <+17>:    sub    $0x88,%rsp                               
=> 0x00007ffff7fe4048 <+24>:    mov    %rdi,-0x78(%rbp)                         
   0x00007ffff7fe404c <+28>:    rdtsc                                           
(gdb) x/16xb $rbp-0x78                                                          
0x7fffffffe488: 0x00    0x00    0x00    0x00    0x00    0x00    0x00    0x00    
0x7fffffffe490: 0x00    0x00    0x00    0x00    0x00    0x00    0x00    0x00    
(gdb) awatch *0x7fffffffe488                                                    
Hardware access (read/write) watchpoint 2: *0x7fffffffe488                      
(gdb) stepi                                                                     

Hardware access (read/write) watchpoint 2: *0x7fffffffe488                      

Old value = 0                                                                   
New value = -6896                                                               
0x00007ffff7fe404c in rtld_timer_start (var=0x7ffff7ffcaa0 <start_time>) at
./elf/rtld.c:85                                                                 
85      in ./elf/rtld.c     


the guest kernel runs properly after above steps inside guest.

My configure:
Host: stable kernel v6.6.8 commit 4c9646a796d66a2d81871a694e88e19a38b115a7
QEMU: v8.1.1 commit 6bb4a8a47a43f35a345f107227fcd6abed59e62c
Guest kernel: kvm tree tags/kvm-6.8-1 commit
1c6d984f523f67ecfad1083bb04c55d91977bb15

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2024-01-10 12:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-04  2:35 [Bug 218339] New: kernel goes unresponsive if single-stepping over an instruction which writes to an address for which a hardware read/write watchpoint has been set bugzilla-daemon
2024-01-04 16:54 ` Sean Christopherson
2024-01-04 16:54 ` [Bug 218339] " bugzilla-daemon
2024-01-04 23:21 ` bugzilla-daemon
2024-01-10 12:38 ` bugzilla-daemon [this message]
2024-01-10 20:21 ` bugzilla-daemon
2024-01-10 21:07 ` bugzilla-daemon
2024-03-05 20:24 ` bugzilla-daemon

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=bug-218339-28872-dvVdfUc8On@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=kvm@vger.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.