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-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAH=s-PNFESLA6TTem-49g0CKsjpKOsj1XYfPUXz6YbEfMWXqXg@mail.gmail.com>
Date:   Wed, 12 Oct 2016 12:16:29 +0100
From:   Yao Qi <qiyaoltc@...il.com>
To:     Pratyush Anand <panand@...hat.com>
Cc:     will.deacon@....com, Mark Rutland <mark.rutland@....com>,
        labath@...gle.com, onestero@...hat.com,
        linux-kernel@...r.kernel.org,
        Jan Kratochvil <jan.kratochvil@...hat.com>,
        linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 3/4] arm64: Allow hw watchpoint of length 3,5,6 and 7

On Wed, Oct 12, 2016 at 6:58 AM, Pratyush Anand <panand@...hat.com> wrote:
> Since, arm64 can support all offset within a double word limit. Therefore,
> now support other lengths within that range as well.

How does ptracer (like GDB) detect kernel has already supported all byte
address select values?  I suppose ptrace(NT_ARM_HW_WATCH, ) with
len is 3 or 5 fail on current kernel but is of success after your patches
applied.

GDB is aware of the byte address select limitation in kernel, so it always
sets 1,2,4,8 in len in ctrl.  GDB needs to know whether the limitation is still
there or not.

-- 
Yao (齐尧)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ