[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAH+eYFAv=UTZ1gQ5jXq8_ziNy1i3BL9y1bOUWMdTow=i3N0n+g@mail.gmail.com>
Date: Tue, 16 Oct 2012 22:29:12 +0200
From: Rabin Vincent <rabin@....in>
To: Oleg Nesterov <oleg@...hat.com>
Cc: linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
Peter Zijlstra <peterz@...radead.org>,
Srikar Dronamraju <srikar@...ux.vnet.ibm.com>
Subject: Re: [PATCH 6/9] uprobes: flush cache after xol write
2012/10/15 Oleg Nesterov <oleg@...hat.com>:
> On 10/14, Rabin Vincent wrote:
>> Flush the cache so that the instructions written to the XOL area are
>> visible.
>>
>> Signed-off-by: Rabin Vincent <rabin@....in>
>> ---
>> kernel/events/uprobes.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/kernel/events/uprobes.c b/kernel/events/uprobes.c
>> index ca000a9..8c52f93 100644
>> --- a/kernel/events/uprobes.c
>> +++ b/kernel/events/uprobes.c
>> @@ -1246,6 +1246,7 @@ static unsigned long xol_get_insn_slot(struct uprobe *uprobe, unsigned long slot
>> offset = current->utask->xol_vaddr & ~PAGE_MASK;
>> vaddr = kmap_atomic(area->page);
>> arch_uprobe_xol_copy(&uprobe->arch, vaddr + offset);
>> + flush_dcache_page(area->page);
>> kunmap_atomic(vaddr);
>
> I agree... but why under kmap_atomic?
No real reason; I'll move it to after the unmap.
--
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/
Powered by blists - more mailing lists