From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: restore get_current() optimisation
Date: Fri, 3 Mar 2017 19:48:47 +0000 [thread overview]
Message-ID: <20170303194846.GA15053@leverpostej> (raw)
In-Reply-To: <515e311c-b044-8759-8bf3-99ac4565840d@nvidia.com>
On Fri, Mar 03, 2017 at 03:32:22PM +0000, Jon Hunter wrote:
> Hi Mark,
>
> On 02/03/17 16:46, Mark Rutland wrote:
> > Perhaps a caller is deriving that from an uninitialised variable? The
> > code and stack layout changes as a result of my patch could easily
> > tickle that.
> You are correct, the reg passed to regcache_flat_read() is indeed dodgy
> and the above BUG() did trip it up.
>
> Commit e411b0b5eb9b ('ASoC: dapm: Support second register for DAPM
> control updates') introduced a 2nd register set into the
> snd_soc_dapm_update struct and if the 'has_second_set' is true then it
> tries to access this register. One of our out-of-tree audio patches was
> not initialising the 'has_second_set' and hence it was trying to write a
> bogus register (need to get this upstream!).
Phew. That's get_current() off the hook!
> I should have caught this, but the bisect threw me off the scent! I
> think that with reverting this patch we were just getting lucky and the
> problem could have still occurred. I went back and tried it again and it
> still works when reverting this change, but its just luck.
>
> Sorry for the noise and thanks for pointing me in the right direction!
No worries; it's always a pain to debug this sort of thing, especially
with a bisect seeming so reliable.
Thanks,
Mark.
next prev parent reply other threads:[~2017-03-03 19:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-03 18:27 [PATCH] arm64: restore get_current() optimisation Mark Rutland
2017-01-04 15:23 ` Will Deacon
2017-03-02 11:35 ` Jon Hunter
2017-03-02 12:35 ` Mark Rutland
2017-03-02 15:30 ` Jon Hunter
2017-03-02 16:12 ` Robin Murphy
2017-03-02 17:11 ` Mark Rutland
2017-03-02 16:46 ` Mark Rutland
2017-03-03 15:32 ` Jon Hunter
2017-03-03 19:48 ` Mark Rutland [this message]
2017-03-02 11:54 ` Andreas Färber
2017-03-02 12:40 ` Mark Rutland
2017-03-02 12:43 ` Andreas Färber
2017-03-02 13:37 ` Mark Rutland
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=20170303194846.GA15053@leverpostej \
--to=mark.rutland@arm.com \
--cc=linux-arm-kernel@lists.infradead.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.