public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Christoph Hellwig <hch@infradead.org>,
	Jaegeuk Kim <jaegeuk@kernel.org>, Chao Yu <yuchao0@huawei.com>,
	Qiuyang Sun <sunqiuyang@huawei.com>,
	Sahitya Tummala <stummala@codeaurora.org>,
	Eric Biggers <ebiggers@google.com>,
	Wang Shilong <wangshilong1991@gmail.com>,
	"Linux F2FS DEV,
	Mailing List"  <linux-f2fs-devel@lists.sourceforge.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Russell King - ARM Linux <linux@armlinux.org.uk>
Subject: Re: [PATCH] f2fs: fix 32-bit linking
Date: Fri, 28 Jun 2019 06:17:38 -0700	[thread overview]
Message-ID: <20190628131738.GA994@infradead.org> (raw)
In-Reply-To: <CAK8P3a1jwPQvX6f+eMZLdnF2ZawDB9obF3hjk2P9RJxDr6HUQA@mail.gmail.com>

On Fri, Jun 28, 2019 at 03:09:47PM +0200, Arnd Bergmann wrote:
> I came across this on arm-nommu (which disables
> CONFIG_CPU_SPECTRE) during randconfig testing.
> 
> I don't see an easy way to add this in there, short of rewriting the
> whole __get_user_err() function. Any suggestions?

Can't we just fall back to using copy_from_user with a little wrapper
that switches based on sizeof()?

  reply	other threads:[~2019-06-28 13:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-28 10:39 [PATCH] f2fs: fix 32-bit linking Arnd Bergmann
2019-06-28 12:44 ` Christoph Hellwig
2019-06-28 13:09   ` Arnd Bergmann
2019-06-28 13:17     ` Christoph Hellwig [this message]
2019-06-28 14:46       ` Arnd Bergmann
2019-06-28 17:58         ` Russell King - ARM Linux admin
2019-07-01 14:58           ` Arnd Bergmann
2019-06-28 23:25   ` Randy Dunlap
2019-06-28 15:59 ` Jaegeuk Kim
2019-07-01 14:54   ` Arnd Bergmann

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=20190628131738.GA994@infradead.org \
    --to=hch@infradead.org \
    --cc=arnd@arndb.de \
    --cc=ebiggers@google.com \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=stummala@codeaurora.org \
    --cc=sunqiuyang@huawei.com \
    --cc=wangshilong1991@gmail.com \
    --cc=yuchao0@huawei.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