From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Doug Anderson <dianders@chromium.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
Pratyush Anand <panand@redhat.com>,
Pavel Labath <labath@google.com>,
LKML <linux-kernel@vger.kernel.org>,
Kazuhiro Inaba <kinaba@google.com>,
Matthias Kaehlcke <mka@chromium.org>,
Guenter Roeck <groeck@chromium.org>,
Will Deacon <will@kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] ARM: hw_breakpoint: Handle inexact watchpoint addresses
Date: Thu, 6 Aug 2020 16:41:44 +0100 [thread overview]
Message-ID: <20200806154144.GD1551@shell.armlinux.org.uk> (raw)
In-Reply-To: <CAD=FV=WgoVN-scgT41R=6Toif2Zrskb3rNzZn_xbP_-ByZC1MA@mail.gmail.com>
On Thu, Aug 06, 2020 at 08:05:10AM -0700, Doug Anderson wrote:
> Hi,
>
> On Mon, Dec 2, 2019 at 8:36 AM Doug Anderson <dianders@chromium.org> wrote:
> >
> > Hi,
> >
> > On Wed, Nov 20, 2019 at 11:18 AM Will Deacon <will@kernel.org> wrote:
> > >
> > > On Sat, Oct 19, 2019 at 11:12:26AM -0700, Douglas Anderson wrote:
> > > > This is commit fdfeff0f9e3d ("arm64: hw_breakpoint: Handle inexact
> > > > watchpoint addresses") but ported to arm32, which has the same
> > > > problem.
> > > >
> > > > This problem was found by Android CTS tests, notably the
> > > > "watchpoint_imprecise" test [1]. I tested locally against a copycat
> > > > (simplified) version of the test though.
> > > >
> > > > [1] https://android.googlesource.com/platform/bionic/+/master/tests/sys_ptrace_test.cpp
> > > >
> > > > Signed-off-by: Douglas Anderson <dianders@chromium.org>
> > > > ---
> > > >
> > > > arch/arm/kernel/hw_breakpoint.c | 96 ++++++++++++++++++++++++---------
> > > > 1 file changed, 70 insertions(+), 26 deletions(-)
> > >
> > > Sorry for taking so long to look at this. After wrapping my head around the
> > > logic again
> >
> > Yeah. It was a little weird and (unfortunately) arbitrarily different
> > in some places compared to the arm64 code.
> >
> >
> > > I think it looks fine, so please put it into the patch system
> > > with my Ack:
> > >
> > > Acked-by: Will Deacon <will@kernel.org>
> >
> > Thanks! Submitted as:
> >
> > https://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=8944/1
>
> Oddly, I found that if I go visit that page now I see:
>
> > - - - Note 2 submitted by Russell King on 17 Jan 2020 11:16:34 (UTC) - - -
> > Moved to applied
> >
> > Applied to git-curr (misc branch).
>
> Yet if I go check mainline the patch is not there. This came to my
> attention since we had my patch picked to the Chrome OS 4.19 tree and
> suddenly recently got a stable merge conflict with "ARM: 8986/1:
> hw_breakpoint: Don't invoke overflow handler on uaccess watchpoints".
>
> Anyone know what happened here?
Yes. Stephen Rothwell raised a complaint against it, which you were
copied with:
> Hi all,
>
> Commit
>
> 116375be0461 ("ARM: 8944/1: hw_breakpoint: Handle inexact watchpoint addresses")
>
> is missing a Signed-off-by from its author.
My reply to Stephen's email was:
> Thanks Stephen, patch dropped.
>
> It looks like Doug used his "m.disordat.com" address to submit the
> patch through the web interface, and there was no From: in the patch
> itself, so that was used as the patch author. However, as you spotted,
> it was signed off using Doug's "chromium.org" address.
>
> I think it's time to make the patch system a bit more strict, checking
> that the submission address is mentioned in a signed-off-by tag
> somewhere in the commit message.
>
> Doug, the patch system does have your "chromium.org" address, if that's
> the one you want to use as the author, please submit using that instead.
> Thanks.
>
> Russell.
Neither email got a response from you, so the patch was dropped and
nothing further happened.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Doug Anderson <dianders@chromium.org>
Cc: Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Pratyush Anand <panand@redhat.com>,
Pavel Labath <labath@google.com>,
LKML <linux-kernel@vger.kernel.org>,
Kazuhiro Inaba <kinaba@google.com>,
Matthias Kaehlcke <mka@chromium.org>,
Guenter Roeck <groeck@chromium.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] ARM: hw_breakpoint: Handle inexact watchpoint addresses
Date: Thu, 6 Aug 2020 16:41:44 +0100 [thread overview]
Message-ID: <20200806154144.GD1551@shell.armlinux.org.uk> (raw)
In-Reply-To: <CAD=FV=WgoVN-scgT41R=6Toif2Zrskb3rNzZn_xbP_-ByZC1MA@mail.gmail.com>
On Thu, Aug 06, 2020 at 08:05:10AM -0700, Doug Anderson wrote:
> Hi,
>
> On Mon, Dec 2, 2019 at 8:36 AM Doug Anderson <dianders@chromium.org> wrote:
> >
> > Hi,
> >
> > On Wed, Nov 20, 2019 at 11:18 AM Will Deacon <will@kernel.org> wrote:
> > >
> > > On Sat, Oct 19, 2019 at 11:12:26AM -0700, Douglas Anderson wrote:
> > > > This is commit fdfeff0f9e3d ("arm64: hw_breakpoint: Handle inexact
> > > > watchpoint addresses") but ported to arm32, which has the same
> > > > problem.
> > > >
> > > > This problem was found by Android CTS tests, notably the
> > > > "watchpoint_imprecise" test [1]. I tested locally against a copycat
> > > > (simplified) version of the test though.
> > > >
> > > > [1] https://android.googlesource.com/platform/bionic/+/master/tests/sys_ptrace_test.cpp
> > > >
> > > > Signed-off-by: Douglas Anderson <dianders@chromium.org>
> > > > ---
> > > >
> > > > arch/arm/kernel/hw_breakpoint.c | 96 ++++++++++++++++++++++++---------
> > > > 1 file changed, 70 insertions(+), 26 deletions(-)
> > >
> > > Sorry for taking so long to look at this. After wrapping my head around the
> > > logic again
> >
> > Yeah. It was a little weird and (unfortunately) arbitrarily different
> > in some places compared to the arm64 code.
> >
> >
> > > I think it looks fine, so please put it into the patch system
> > > with my Ack:
> > >
> > > Acked-by: Will Deacon <will@kernel.org>
> >
> > Thanks! Submitted as:
> >
> > https://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=8944/1
>
> Oddly, I found that if I go visit that page now I see:
>
> > - - - Note 2 submitted by Russell King on 17 Jan 2020 11:16:34 (UTC) - - -
> > Moved to applied
> >
> > Applied to git-curr (misc branch).
>
> Yet if I go check mainline the patch is not there. This came to my
> attention since we had my patch picked to the Chrome OS 4.19 tree and
> suddenly recently got a stable merge conflict with "ARM: 8986/1:
> hw_breakpoint: Don't invoke overflow handler on uaccess watchpoints".
>
> Anyone know what happened here?
Yes. Stephen Rothwell raised a complaint against it, which you were
copied with:
> Hi all,
>
> Commit
>
> 116375be0461 ("ARM: 8944/1: hw_breakpoint: Handle inexact watchpoint addresses")
>
> is missing a Signed-off-by from its author.
My reply to Stephen's email was:
> Thanks Stephen, patch dropped.
>
> It looks like Doug used his "m.disordat.com" address to submit the
> patch through the web interface, and there was no From: in the patch
> itself, so that was used as the patch author. However, as you spotted,
> it was signed off using Doug's "chromium.org" address.
>
> I think it's time to make the patch system a bit more strict, checking
> that the submission address is mentioned in a signed-off-by tag
> somewhere in the commit message.
>
> Doug, the patch system does have your "chromium.org" address, if that's
> the one you want to use as the author, please submit using that instead.
> Thanks.
>
> Russell.
Neither email got a response from you, so the patch was dropped and
nothing further happened.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2020-08-06 15:46 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-19 18:12 [PATCH] ARM: hw_breakpoint: Handle inexact watchpoint addresses Douglas Anderson
2019-10-19 18:12 ` Douglas Anderson
2019-10-21 18:46 ` Matthias Kaehlcke
2019-10-21 18:46 ` Matthias Kaehlcke
2019-10-21 23:49 ` Doug Anderson
2019-10-21 23:49 ` Doug Anderson
2019-10-22 16:39 ` Matthias Kaehlcke
2019-10-22 16:39 ` Matthias Kaehlcke
2019-11-20 19:18 ` Will Deacon
2019-11-20 19:18 ` Will Deacon
2019-12-02 16:36 ` Doug Anderson
2019-12-02 16:36 ` Doug Anderson
2020-01-06 17:40 ` Will Deacon
2020-01-06 17:40 ` Will Deacon
2020-08-06 15:05 ` Doug Anderson
2020-08-06 15:05 ` Doug Anderson
2020-08-06 15:41 ` Russell King - ARM Linux admin [this message]
2020-08-06 15:41 ` Russell King - ARM Linux admin
2020-08-06 15:45 ` Doug Anderson
2020-08-06 15:45 ` Doug Anderson
2020-08-06 18:28 ` Doug Anderson
2020-08-06 18:28 ` Doug Anderson
2020-08-06 22:02 ` Russell King - ARM Linux admin
2020-08-06 22:02 ` Russell King - ARM Linux admin
2020-08-06 22:26 ` Doug Anderson
2020-08-06 22:26 ` Doug Anderson
2020-08-06 22:28 ` Russell King - ARM Linux admin
2020-08-06 22:28 ` Russell King - ARM Linux admin
2020-08-06 16:16 ` Russell King - ARM Linux admin
2020-08-06 16:16 ` Russell King - ARM Linux admin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200806154144.GD1551@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=dianders@chromium.org \
--cc=groeck@chromium.org \
--cc=kinaba@google.com \
--cc=labath@google.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mka@chromium.org \
--cc=panand@redhat.com \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.