summaryrefslogtreecommitdiffstats
path: root/arch/arm/mach-s3c24xx
diff options
context:
space:
mode:
authorOleg Nesterov <oleg@redhat.com>2012-09-29 21:56:57 +0200
committerAnton Arapov <anton@redhat.com>2012-10-29 11:50:18 +0100
commit37b37814b30dcef5f2180bbcc7395782eed0ef23 (patch)
treefb20879a9370eab4aa17403216bdaab847ff8fdc /arch/arm/mach-s3c24xx
parent465c67c45914452db4b13cbb493e452abbb25d5e (diff)
downloadkernel-uprobes-37b37814b30dcef5f2180bbcc7395782eed0ef23.tar.gz
kernel-uprobes-37b37814b30dcef5f2180bbcc7395782eed0ef23.tar.xz
kernel-uprobes-37b37814b30dcef5f2180bbcc7395782eed0ef23.zip
uprobes: Fix handle_swbp() vs unregister() + register() race
Strictly speaking this race was added by me in 56bb4cf6. However I think that this bug is just another indication that we should move copy_insn/uprobe_analyze_insn code from install_breakpoint() to uprobe_register(), there are a lot of other reasons for that. Until then, add a hack to close the race. A task can hit uprobe U1, but before it calls find_uprobe() this uprobe can be unregistered *AND* another uprobe U2 can be added to uprobes_tree at the same inode/offset. In this case handle_swbp() will use the not-fully-initialized U2, in particular its arch.insn for xol. Add the additional !UPROBE_COPY_INSN check into handle_swbp(), if this flag is not set we simply restart as if the new uprobe was not inserted yet. This is not very nice, we need barriers, but we will remove this hack when we change uprobe_register(). Note: with or without this patch install_breakpoint() can race with itself, yet another reson to kill UPROBE_COPY_INSN altogether. And even the usage of uprobe->flags is not safe. See the next patches. Signed-off-by: Oleg Nesterov <oleg@redhat.com> Acked-by: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
Diffstat (limited to 'arch/arm/mach-s3c24xx')
0 files changed, 0 insertions, 0 deletions