From: Peter Rosin <peda@axentia.se>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
"'linux-arm-kernel@lists.infradead.org'"
<linux-arm-kernel@lists.infradead.org>,
"nico@fluxnic.net" <nico@fluxnic.net>,
Will Deacon <will.deacon@arm.com>,
"torvalds@linux-foundation.org" <torvalds@linux-foundation.org>
Subject: RE: Domain faults when CONFIG_CPU_SW_DOMAIN_PAN is enabled
Date: Wed, 30 Dec 2015 16:51:37 +0000 [thread overview]
Message-ID: <bc5dfe76333842f8af88862826b16571@EMAIL.axentia.se> (raw)
In-Reply-To: <20151210162054.GM8644@n2100.arm.linux.org.uk>
[I repeat myself just in case my last message disappeared. It would be
a shame if 4.4 was also regressed because of a missing response.]
I wrote:
> Russell King wrote:
> > On Thu, Dec 10, 2015 at 03:29:37PM +0000, Peter Rosin wrote:
> > > Russell King wrote:
> > > > On Thu, Dec 03, 2015 at 09:37:51PM +0000, Peter Rosin wrote:
> > > > > I took both patches for a quick spin (a dozen boots and one hour
> > > > > uptime after that for each patch) and no incidents. I have not
> > > > > gathered data, but the crash on boot feels like it's quite a bit
> > > > > above 50% when there is a problem so this feels good (I used 5
> > > > > clean reboots when I bisected and that worked).
> > > > >
> > > > > Reported-by: Peter Rosin <peda@axentia.se>
> > > > > Tested-by: Peter Rosin <peda@axentia.se>
> > > > >
> > > > > (and please don't forget to cc stable)
> > > >
> > > > I've decided to do a more in-depth fix, so that we also solve the
> > > > issue that when we schedule in these down_read()s, we don't leak
> > > > the permissive domain register setting into the switched-to context.
> > > >
> > > > Can you test this patch please? Thanks.
> > >
> > > Still looking good.
> >
> > Does that mean I can add your reported and tested-by to this latest patch?
>
> Right, I thought that was obvious, sorry for the confusion.
Reported-by: Peter Rosin <peda@axentia.se>
Tested-by: Peter Rosin <peda@axentia.se>
(and please don't forget to cc stable)
Cheers,
Peter
next prev parent reply other threads:[~2015-12-30 16:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-03 8:33 Peter Rosin
2015-12-03 11:00 ` Russell King - ARM Linux
2015-12-03 11:38 ` Peter Rosin
2015-12-03 11:51 ` Russell King - ARM Linux
2015-12-03 12:08 ` Peter Rosin
2015-12-03 13:37 ` Russell King - ARM Linux
2015-12-03 16:12 ` Peter Rosin
2015-12-03 16:41 ` Russell King - ARM Linux
2015-12-03 17:27 ` Russell King - ARM Linux
2015-12-03 18:28 ` Nicolas Pitre
2015-12-05 13:41 ` Russell King - ARM Linux
2015-12-03 21:37 ` Peter Rosin
2015-12-10 0:22 ` Russell King - ARM Linux
2015-12-10 15:29 ` Peter Rosin
2015-12-10 16:20 ` Russell King - ARM Linux
2015-12-10 18:32 ` Peter Rosin
2015-12-30 16:51 ` Peter Rosin [this message]
2015-12-30 16:57 ` Peter Rosin
-- strict thread matches above, loose matches on Subject: below --
2015-12-03 7:43 Peter Rosin
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=bc5dfe76333842f8af88862826b16571@EMAIL.axentia.se \
--to=peda@axentia.se \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=nico@fluxnic.net \
--cc=torvalds@linux-foundation.org \
--cc=will.deacon@arm.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®