[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+55aFzeNvdu1E0VrmZ=p8eJL-vZ4no-qJ=PaBaBg0JLAMSsFg@mail.gmail.com>
Date: Sun, 21 May 2017 14:37:15 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Al Viro <viro@...iv.linux.org.uk>
Cc: kernel test robot <xiaolong.ye@...el.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...nel.org>,
Oleg Nesterov <oleg@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
Christoph Hellwig <hch@....de>, LKP <lkp@...org>
Subject: Re: [lkp-robot] [waitid()] 75f64d68f9: Kernel_panic-not_syncing:Attempted_to_kill_init!exitcode=
On Sun, May 21, 2017 at 2:14 PM, Al Viro <viro@...iv.linux.org.uk> wrote:
>
> Umm... get_user() for anything larger than long is simply not supported on
> a lot of architectures[1]. Do we really want to do that for unsafe_get_user()?
I'm pretty sure there's a reason we added support for it on x86-32,
because there are structures that use __u64 and fill things one entry
at a time.
It's entirely possible that that code then fails (maybe it compiles,
but doesn't work) on various other architectures. There's a lot of
drivers that are disabled on non-x86.
Linus
Powered by blists - more mailing lists