Re: [PATCH V2 3/5] arm64: hw_breakpoint: Handle inexact watchpoint addresses

2016-11-08 Thread Pavel Labath
>> >> /* Do we need to handle the stepping? */ >> if (is_default_overflow_handler(wp)) >> step = 1; >> - >> -unlock: >> - rcu_read_unlock(); >> } >> + if (min_dist > 0 && min_dist != -1) { >> + /* No exact match fou

Re: [PATCH 3/4] arm64: Allow hw watchpoint of length 3,5,6 and 7

2016-10-13 Thread Pavel Labath
On 13 October 2016 at 11:22, Pratyush Anand wrote: > > > On Wednesday 12 October 2016 04:46 PM, Yao Qi wrote: >> >> On Wed, Oct 12, 2016 at 6:58 AM, Pratyush Anand wrote: >>> >>> Since, arm64 can support all offset within a double word limit. >>> Therefore, >>> now support other lengths within th

Re: ptrace and pseudoterminals

2015-11-18 Thread Pavel Labath
On 5 November 2015 at 20:29, Peter Hurley wrote: > On 11/05/2015 01:35 PM, Pavel Labath wrote: >> That said, it seems to me that this could be a generally useful >> feature. For the test suite, I can insert a sleep (even a large one, >> to be sure), but this seems like a sub

Re: ptrace and pseudoterminals

2015-11-05 Thread Pavel Labath
On 5 November 2015 at 05:25, Peter Hurley wrote: > On 11/04/2015 02:43 PM, Oleg Nesterov wrote: >> Oh, I don't think "Automagically if ptrace" makes any sense... What makes >> ptrace special? Afaics nothing. >> >> We can modify this test-case to use signals/futexes/whatever to let the >> the paren

ptrace and pseudoterminals

2015-11-03 Thread Pavel Labath
Hello Oleg, everyone, I have noticed something, which may be considered a race in the interaction of ptrace and pseudoterminal interfaces. Basically, what happens is this: - we have two processes: A and B. B has the slave end of the pty open, A has the master. A is tracing B. - B writes some data

Re: A peculiarity in ptrace/waitpid behavior

2015-03-24 Thread Pavel Labath
(eventually) reported? cheers, pl On 23 March 2015 at 09:42, Pavel Labath wrote: > On 21 March 2015 at 18:57, Oleg Nesterov wrote: >> On 03/20, Pavel Labath wrote: >>> >>> One difference I see though is that in >>> our test, we are not sending any additional signals to

Re: A peculiarity in ptrace/waitpid behavior

2015-03-23 Thread Pavel Labath
On 21 March 2015 at 18:57, Oleg Nesterov wrote: > On 03/20, Pavel Labath wrote: >> >> One difference I see though is that in >> our test, we are not sending any additional signals to the thread in >> question (at least we shouldn't be sending them, but we are

Re: A peculiarity in ptrace/waitpid behavior

2015-03-20 Thread Pavel Labath
Sending again, this time as plain text (I hope)... On 20 March 2015 at 18:46, Pavel Labath wrote: > > Hi, > > thanks for the super quick response. :) > > I am at home now, so I don't have access to the same machine to run the test. > I will run it on monday and let