BMC/Intel-BMC/linux.git/lib/iov_iter.c, branch dev-4.7

fix iov_iter_fault_in_readable()

2016-09-24T08:09:38+00:00

commit d4690f1e1cdabb4d61207b6787b1605a0dc0aeab upstream. ... by turning it into what used to be multipages counterpart Signed-off-by: Al Viro Signed-off-by: Linus Torvalds Signed-off-by: Greg Kroah-Hartman

Merge branch 'work.iov_iter' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs

2016-05-25T22:59:09+00:00

Pull vfs iov_iter regression fix from Al Viro: "Fix for braino in 'fold checks into iterate_and_advance()'" * 'work.iov_iter' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs: do "fold checks into iterate_and_advance()" right

do "fold checks into iterate_and_advance()" right

2016-05-25T22:16:02+00:00

the only case when we should skip the iterate_and_advance() guts is when nothing's left in the iterator, _not_ just when requested amount is 0. Said guts will do nothing in the latter case anyway; the problem we tried to deal with in the aforementioned commit is that when there's nothing left *and* the amount requested is 0, we might end up deferencing one iovec too many; the value we fetch from there is discarded in that case, but theoretically it might oops if the iovec array ends exactly at the end of page with the next page not mapped. Bailing out on zero size requested had an unexpected side effect - zero-length segment in the beginning of iovec array ended up throwing do_loop_readv_writev() into infinite spin; we do not advance past the empty segment at all. Reproducer is trivial: echo '#include ' >a.c echo 'main() {char c; struct iovec v[] = {{&c,0},{&c,1}}; readv(0,v,2);}' >>a.c cc a.c && ./a.out

Merge branch 'work.iov_iter' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs

2016-05-18T18:46:23+00:00

Pull iov_iter cleanups from Al Viro. * 'work.iov_iter' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs: fold checks into iterate_and_advance() rw_verify_area(): saner calling conventions aio: remove a pointless assignment

fold checks into iterate_and_advance()

2016-05-09T18:04:29+00:00

they are open-coded in all users except iov_iter_advance(), and there they wouldn't be a bad idea either - as it is, iov_iter_advance(i, 0) ends up dereferencing potentially past the end of iovec array. It doesn't do anything with the value it reads, and very unlikely to trigger an oops on dereference, but it is not impossible. Reported-by: Jiri Slaby Reported-by: Takashi Iwai Signed-off-by: Al Viro

fix the copy vs. map logics in blk_rq_map_user_iov()

2016-04-08T23:46:28+00:00

Signed-off-by: Al Viro

iov_iter: export import_single_range()

2015-12-07T01:42:19+00:00

Signed-off-by: Al Viro

iov_iter: constify {csum_and_,}copy_to_iter()

2015-12-07T01:42:15+00:00

Signed-off-by: Al Viro

Merge branch 'iov_iter' into for-next

2015-04-12T02:26:51+00:00

VFS: Add iov_iter_fault_in_multipages_readable()

2015-04-12T02:24:32+00:00

simillar to iov_iter_fault_in_readable() but differs in that it is not limited to faulting in the first iovec and instead faults in "bytes" bytes iterating over the iovecs as necessary. Also, instead of only faulting in the first and last page of the range, all pages are faulted in. This function is needed by NTFS when it does multi page file writes. Signed-off-by: Anton Altaparmakov Signed-off-by: Al Viro