linux-kernel - kgdb with sw single-step...

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20080429.010221.268320653.davem@davemloft.net>
Date:	Tue, 29 Apr 2008 01:02:21 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	linux-kernel@...r.kernel.org
Subject: kgdb with sw single-step...

While working on the sparc port of the new kgdb code in the tree I ran
across a fundamental issue with this stuff on cpus that do
single-stepping in software.

The short story is that since such sw single-stepping is using
globally visible state (the temporary breakpoint used), it does not
fare well in the presence of cpus other than the current one hitting
the single-step breakpoint.

This actually limits my ability to test using kgdbts fully, the
parallel tests often fail because the sw single-step emulation
in kgdbts runs into several issues including the one I'm
mentioning here.

The good news is that there is a mostly working solution possible.

When GDB is handling a normal threaded process, it handles other
threads tripping over the temporary single-step breakpoint by simply
holding them stopped until the thread that should have hit the
breakpoint, does hit it.

The kernel could do something similar, but this would require
something like:

1) The architecture kgdb support code implements the sw single
   step breakpoint logic, this is necessary in order to
   handle single stepping over branches, calls, and things
   of this nature.  (this is something the single-step
   emulation code in kgdbts doesn't even try to get right).

2) The kgdb stub implements the single-stepping command using
   the support code in #1.  When this happens, foreign cpus
   which have been captured are kept captured until the
   single-step breakpoint it hit by the primary kgdb cpu.

Of course, this means we'll need changes to how gdb talks over the
stub on these processors (mips, arm, sparc, etc.)  since currently gdb
will do all of the sw single-step breakpoint work.

Some architectures, like Alpha, do the single-stepping in the
ptrace implementation.  Basically it's doing all of the sw
single-step breakpoint work on the kernel side, instead of
in gdb.  Platforms like Alpha would therefore be readily adaptable
to the above scheme without any gdb changes.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/