Intel OpenBMC Linux kernel source tree (mirror) https://git.radix-linux.su/BMC/Intel-BMC/linux.git/atom?h=dev-4.17 2018-07-03T09:27:03+00:00 2018-07-03T09:27:03+00:00 Silvio Cesare silvio.cesare@gmail.com 2018-05-04T03:44:02+00:00 urn:sha1:d49a9fd028016b74f61ebbd98e41cbc899f2df93 commit 353748a359f1821ee934afc579cf04572406b420 upstream. There is potential for the size and len fields in ubifs_data_node to be too large causing either a negative value for the length fields or an integer overflow leading to an incorrect memory allocation. Likewise, when the len field is small, an integer underflow may occur. Signed-off-by: Silvio Cesare <silvio.cesare@gmail.com> Fixes: 1e51764a3c2ac ("UBIFS: add new flash file system") Cc: stable@vger.kernel.org Signed-off-by: Kees Cook <keescook@chromium.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> 2018-04-11T23:39:34+00:00 Linus Torvalds torvalds@linux-foundation.org 2018-04-11T23:39:34+00:00 urn:sha1:77cb51e65df0010cb22169bcbb6ea1b4f21da7e0 Pull UBI and UBIFS updates from Richard Weinberger: "Minor bug fixes and improvements" * tag 'tags/upstream-4.17-rc1' of git://git.infradead.org/linux-ubifs: ubi: Reject MLC NAND ubifs: Remove useless parameter of lpt_heap_replace ubifs: Constify struct ubifs_lprops in scan_for_leb_for_idx ubifs: remove unnecessary assignment ubi: Fix error for write access ubi: fastmap: Don't flush fastmap work on detach ubifs: Check ubifs_wbuf_sync() return code 2018-04-04T21:48:11+00:00 Jiang Biao jiang.biao2@zte.com.cn 2018-02-28T02:22:37+00:00 urn:sha1:4fb1cd82302e2aa87bb4876d67f3ed679f1f4a04 The parameter *old_lprops* is never used in lpt_heap_replace(), remove it to avoid compile warning. Signed-off-by: Jiang Biao <jiang.biao2@zte.com.cn> Signed-off-by: Richard Weinberger <richard@nod.at> 2018-04-04T21:48:10+00:00 Jiang Biao jiang.biao2@zte.com.cn 2018-02-28T02:13:57+00:00 urn:sha1:cc1947834827379a5fd66e8b73969fd7eaab4516 Constify struct ubifs_lprops in scan_for_leb_for_idx to be consistent with other references. Signed-off-by: Jiang Biao <jiang.biao2@zte.com.cn> Signed-off-by: Richard Weinberger <richard@nod.at> 2018-04-04T21:48:10+00:00 Stefan Agner stefan@agner.ch 2018-02-11T22:17:36+00:00 urn:sha1:ae4c8081eb77bc82ac5ac8a7d55abea6f98e0209 Assigning a value of a variable to itself is not useful. This fixes a warning shown when using clang: warning: explicitly assigning value of variable of type 'int' to itself [-Wself-assign] Signed-off-by: Stefan Agner <stefan@agner.ch> Signed-off-by: Richard Weinberger <richard@nod.at> 2018-04-04T21:41:44+00:00 Richard Weinberger richard@nod.at 2018-01-17T18:12:42+00:00 urn:sha1:aac17948a7ce01fb60b9ee6cf902967a47b3ce26 If ubifs_wbuf_sync() fails we must not write a master node with the dirty marker cleared. Otherwise it is possible that in case of an IO error while syncing we mark the filesystem as clean and UBIFS refuses to recover upon next mount. Cc: <stable@vger.kernel.org> Fixes: 1e51764a3c2a ("UBIFS: add new flash file system") Signed-off-by: Richard Weinberger <richard@nod.at> 2018-03-28T05:39:02+00:00 Christoph Hellwig hch@lst.de 2018-02-21T15:54:48+00:00 urn:sha1:f35562549ff9ecb9114f380843b3ac778c2a781e I_DIRTY_DATASYNC is a strict superset of I_DIRTY_SYNC semantics, as in mark dirty to be written out by fdatasync as well. So dirtying for both flags makes no sense. Signed-off-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk> 2018-02-04T18:43:12+00:00 Linus Torvalds torvalds@linux-foundation.org 2018-02-04T18:43:12+00:00 urn:sha1:3462ac57033e79a87dbae2497773f22b9c536fbc Pull fscrypt updates from Ted Ts'o: "Refactor support for encrypted symlinks to move common code to fscrypt" Ted also points out about the merge: "This makes the f2fs symlink code use the fscrypt_encrypt_symlink() from the fscrypt tree. This will end up dropping the kzalloc() -> f2fs_kzalloc() change, which means the fscrypt-specific allocation won't get tested by f2fs's kmalloc error injection system; which is fine" * tag 'fscrypt_for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tytso/fscrypt: (26 commits) fscrypt: fix build with pre-4.6 gcc versions fscrypt: remove 'ci' parameter from fscrypt_put_encryption_info() fscrypt: document symlink length restriction fscrypt: fix up fscrypt_fname_encrypted_size() for internal use fscrypt: define fscrypt_fname_alloc_buffer() to be for presented names fscrypt: calculate NUL-padding length in one place only fscrypt: move fscrypt_symlink_data to fscrypt_private.h fscrypt: remove fscrypt_fname_usr_to_disk() ubifs: switch to fscrypt_get_symlink() ubifs: switch to fscrypt ->symlink() helper functions ubifs: free the encrypted symlink target f2fs: switch to fscrypt_get_symlink() f2fs: switch to fscrypt ->symlink() helper functions ext4: switch to fscrypt_get_symlink() ext4: switch to fscrypt ->symlink() helper functions fscrypt: new helper function - fscrypt_get_symlink() fscrypt: new helper functions for ->symlink() fscrypt: trim down fscrypt.h includes fscrypt: move fscrypt_is_dot_dotdot() to fs/crypto/fname.c fscrypt: move fscrypt_valid_enc_modes() to fscrypt_private.h ... 2018-01-17T23:18:49+00:00 Rock Lee rli@sierrawireless.com 2018-01-11T02:08:24+00:00 urn:sha1:b3e73839379327ee21240ac48ea9a2eaf7613d79 There is a situation that other modules, like overlayfs, try to get xattr value with a small buffer, if they get -ERANGE, they will try again with the proper buffer size. No need to report an error. Signed-off-by: Rock Lee <rli@sierrawireless.com> Signed-off-by: Richard Weinberger <richard@nod.at> 2018-01-17T20:48:05+00:00 Eric Biggers ebiggers@google.com 2017-11-29T20:43:17+00:00 urn:sha1:252153ba518ac0bcde6b7152c63380d4415bfe5d Signed-off-by: Eric Biggers <ebiggers@google.com> Signed-off-by: Richard Weinberger <richard@nod.at>