All of lore.kernel.org
 help / color / mirror / Atom feed
From: huawei.libin@huawei.com (Li Bin)
To: linux-arm-kernel@lists.infradead.org
Subject: [BUG] arm64/hw_breakpoint: trigger breakpoint exception infinitely
Date: Tue, 26 Apr 2016 16:23:19 +0800	[thread overview]
Message-ID: <571F2577.2080203@huawei.com> (raw)

This bug can be reproduced by compiling the hw_breakpoint sample
module that is in the kernel tree, when loading it with parameter
ksym=nfsdstats, and running nfsstat:

$ insmod data_breakpoint.ko ksym=nfsdstats
$ nfsstat

It will trigger breakpoint exception infinitely:

nfsdstats value is changed
...
Call trace:
...
Dump stack from sample_hbp_handler
nfsdstats value is changed
...
Call trace:
...
Dump stack from sample_hbp_handler
......
......

This is because that the overflow_handler is set to the callback
in the module, and in watchpoint_handler, it will not disable the
breakpoint (and set single step that reenable it), so when exception
return, it will trigger the breakpoint exception again immediately...


Li Bin

             reply	other threads:[~2016-04-26  8:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-26  8:23 Li Bin [this message]
2016-04-26 12:22 ` [BUG] arm64/hw_breakpoint: trigger breakpoint exception infinitely Will Deacon
2016-04-27  2:35   ` Li Bin

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=571F2577.2080203@huawei.com \
    --to=huawei.libin@huawei.com \
    --cc=linux-arm-kernel@lists.infradead.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.