From: will.deacon@arm•com (Will Deacon)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 00/11] Fix arm64 issues highlighted by sparse and smatch
Date: Tue, 26 Aug 2014 18:05:29 +0100 [thread overview]
Message-ID: <20140826170529.GZ23445@arm.com> (raw)
In-Reply-To: <20140826145614.GE6689@cbox>
Hi Christoffer,
On Tue, Aug 26, 2014 at 03:56:14PM +0100, Christoffer Dall wrote:
> On Tue, Aug 26, 2014 at 03:13:19PM +0100, Will Deacon wrote:
> > Hi all,
> >
> > After the static checking talk at kernel summit, I felt empowered to go
> > and run sparse and smatch over the arm64 defconfig. As I anticipated,
> > this spotted a few issues in the arch code, so I've fixed up the ones
> > that aren't just noise in this series. Most are simply incorrect
> > address space annotations, but fixing these is useful for spotting real
> > issues in the future.
> >
> > I don't think any of these fix critical bugs, but they all deserve to be
> > addressed. I tagged the compat watchpoint fix for stable, as that code
> > has been broken since we merged the architecture port.
> >
>
> Do you want me to queue the kvm ones or did you have other plans to
> upstream this entire series as one?
They're all independent, so please take the kvm ones via your tree. I can
send a separate pull if you prefer? Jason -- would you like an
irqchip-specific pull for those?
> Also, do you consider these fixes for 3.17 (what about cc for stable in
> that case), or for 3.18?
The only one I CC'd stable for was the compat ptrace watchpoint patch,
because that's something that we've been getting wrong and will cause
breakage with a 32-bit GDB. I don't consider the others urgent (i.e. happy
if you wait until 3.18).
Cheers,
Will
next prev parent reply other threads:[~2014-08-26 17:05 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-26 14:13 [PATCH 00/11] Fix arm64 issues highlighted by sparse and smatch Will Deacon
2014-08-26 14:13 ` [PATCH 01/11] KVM: ARM/arm64: fix non-const declaration of function returning const Will Deacon
2014-08-26 14:21 ` Marc Zyngier
2014-08-26 14:29 ` Christoffer Dall
2014-08-26 14:13 ` [PATCH 02/11] KVM: ARM/arm64: fix broken __percpu annotation Will Deacon
2014-08-26 14:21 ` Marc Zyngier
2014-08-26 14:13 ` [PATCH 03/11] KVM: ARM/arm64: avoid returning negative error code as bool Will Deacon
2014-08-26 14:22 ` Marc Zyngier
2014-08-26 14:49 ` Christoffer Dall
2014-08-26 14:13 ` [PATCH 04/11] KVM: ARM/arm64: return -EFAULT if copy_from_user fails in set_timer_reg Will Deacon
2014-08-26 14:22 ` Marc Zyngier
2014-08-26 14:49 ` Christoffer Dall
2014-08-26 14:13 ` [PATCH 05/11] KVM: vgic: return int instead of bool when checking I/O ranges Will Deacon
2014-08-26 14:27 ` Marc Zyngier
2014-08-26 14:49 ` Christoffer Dall
2014-08-26 14:13 ` [PATCH 06/11] KVM: vgic: declare probe function pointer as const Will Deacon
2014-08-26 14:27 ` Marc Zyngier
2014-08-26 14:50 ` Christoffer Dall
2014-08-26 14:13 ` [PATCH 07/11] irqchip: gic: make gic_default_routable_irq_domain_ops static Will Deacon
2014-08-26 14:29 ` Marc Zyngier
2014-08-26 14:13 ` [PATCH 08/11] irqchip: gic-v3: declare rdist as __percpu pointer to __iomem pointer Will Deacon
2014-08-26 14:29 ` Marc Zyngier
2014-08-26 14:13 ` [PATCH 09/11] arm64: ptrace: fix compat hardware watchpoint reporting Will Deacon
2014-08-26 14:13 ` [PATCH 10/11] arm64: ptrace: fix compat reg getter/setter return values Will Deacon
2014-08-26 14:13 ` [PATCH 11/11] arm64: perf: don't rely on layout of pt_regs when grabbing sp or pc Will Deacon
2014-08-26 14:43 ` Jean Pihet
2014-08-26 14:56 ` [PATCH 00/11] Fix arm64 issues highlighted by sparse and smatch Christoffer Dall
2014-08-26 17:05 ` Will Deacon [this message]
2014-08-27 20:58 ` Christoffer Dall
2014-09-03 12:10 ` Jason Cooper
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=20140826170529.GZ23445@arm.com \
--to=will.deacon@arm$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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