[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160728003102.GS2356@ZenIV.linux.org.uk>
Date: Thu, 28 Jul 2016 01:31:02 +0100
From: Al Viro <viro@...IV.linux.org.uk>
To: David Miller <davem@...emloft.net>
Cc: alexmcwhirter@...adic.us, rlwinm@....org, chunkeey@...glemail.com,
linux-wireless@...r.kernel.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: PROBLEM: network data corruption (bisected to e5a4b0bb803b)
On Wed, Jul 27, 2016 at 04:45:43PM -0700, David Miller wrote:
> > I highly expect both my issue and OP's issue to revolve not around
> > commit e5a4b0bb803b specifically, but around other code that no longer
> > behaves as expected because of it.
>
> Indeed, and that fault address rounding bug occurs two other times
> in arch/sparc/lib/user_fixup.c
>
> The mentioned patchwork patch should fix the bug and I'll get that
> into my sparc tree, merged, and queued up for -stable ASAP.
Plausible for sparc, but I don't see similar __copy_to_user_inatomic()
bugs in case of x86_64...
Powered by blists - more mailing lists