> Cosmetic. __set_bit(UPROBE_SKIP_SSTEP) is the part of initialization, > it is not clear why it is set in insert_uprobe(). > > Signed-off-by: Oleg Nesterov <o...@redhat.com> Acked-by: Srikar Dronamraju <sri...@linux.vnet.ibm.com>
> --- > kernel/events/uprobes.c | 5 ++--- > 1 files changed, 2 insertions(+), 3 deletions(-) > > diff --git a/kernel/events/uprobes.c b/kernel/events/uprobes.c > index 5e22faf..e9f22ed 100644 > --- a/kernel/events/uprobes.c > +++ b/kernel/events/uprobes.c > @@ -430,9 +430,6 @@ static struct uprobe *insert_uprobe(struct uprobe *uprobe) > u = __insert_uprobe(uprobe); > spin_unlock(&uprobes_treelock); > > - /* For now assume that the instruction need not be single-stepped */ > - __set_bit(UPROBE_SKIP_SSTEP, &uprobe->flags); > - > return u; > } > > @@ -454,6 +451,8 @@ static struct uprobe *alloc_uprobe(struct inode *inode, > loff_t offset) > uprobe->offset = offset; > init_rwsem(&uprobe->consumer_rwsem); > mutex_init(&uprobe->copy_mutex); > + /* For now assume that the instruction need not be single-stepped */ > + __set_bit(UPROBE_SKIP_SSTEP, &uprobe->flags); > > /* add to uprobes_tree, sorted on inode:offset */ > cur_uprobe = insert_uprobe(uprobe); > -- > 1.5.5.1 > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/