From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: [git pull] uaccess __copy_from_user
Date: Mon, 1 Jun 2020 19:31:03 +0100 [thread overview]
Message-ID: <20200601183103.GE23230@ZenIV.linux.org.uk> (raw)
Getting rid of __copy_from_user() callers -
patches that don't fit into other series
The following changes since commit 8f3d9f354286745c751374f5f1fcafee6b3f3136:
Linux 5.7-rc1 (2020-04-12 12:35:55 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git uaccess.__copy_from_user
for you to fetch changes up to ff847781049c37dff9ad4af2bf2d7aad02622f96:
pstore: switch to copy_from_user() (2020-04-23 10:52:48 -0400)
----------------------------------------------------------------
Al Viro (2):
firewire: switch ioctl_queue_iso to use of copy_from_user()
pstore: switch to copy_from_user()
drivers/firewire/core-cdev.c | 4 +---
fs/pstore/ram_core.c | 4 +---
2 files changed, 2 insertions(+), 6 deletions(-)
next reply other threads:[~2020-06-01 18:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-01 18:31 Al Viro [this message]
2020-06-01 23:55 ` [git pull] uaccess __copy_from_user pr-tracker-bot
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=20200601183103.GE23230@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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