linux-kernel - [PATCHv2 0/9] vme_user checkpatch fixes and read()/write() rework

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1435075419-28211-1-git-send-email-dmitry.kalinkin@gmail.com>
Date:	Tue, 23 Jun 2015 19:03:30 +0300
From:	Dmitry Kalinkin <dmitry.kalinkin@...il.com>
To:	linux-kernel@...r.kernel.org, devel@...verdev.osuosl.org
Cc:	Martyn Welch <martyn.welch@...com>,
	Manohar Vanga <manohar.vanga@...il.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Dmitry Kalinkin <dmitry.kalinkin@...il.com>
Subject: [PATCHv2 0/9] vme_user checkpatch fixes and read()/write() rework

First four patches are fixes for various checpatch warnings.  Next there is a
change to drop large read()/write() stub followed by a change to rework user
copy error codes.  Last three changes are refactorings.

v2 fixes  ("vme_user: return -EFAULT on __copy_*_user errors") that had EINVAL
instead of EFAULT in a couple of places.

Dmitry Kalinkin (9):
  staging: vme_user: fix code alignment
  staging: vme_user: fix blank lines
  staging: vme_user: fix NULL comparison style
  staging: vme_user: fix kmalloc style
  staging: vme_user: allow large read()/write()
  staging: vme_user: return -EFAULT on __copy_*_user errors
  staging: vme_user: remove unused variable
  staging: vme_user: remove distracting comment
  staging: vme_user: remove okcount variable

 drivers/staging/vme/devices/vme_user.c | 158 +++++++++++----------------------
 1 file changed, 51 insertions(+), 107 deletions(-)

-- 
1.8.3.1

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/