{"push_id":2410316193,"size":78,"distinct_size":78,"ref":"refs/heads/star-x2","head":"884f2254464ff17cfc711b89f0a619bae42e3a48","before":"feeff2b235b810245bbb83368f5e1f3b10b31eff","commits":[{"sha":"5d06629e1087d28f49cc36b1a5383fd21cb1edef","author":{"name":"Alex Shi","email":"86471483ef45d8c07197ca74d2a2a81eaf9f0582@linaro.org"},"message":" Merge tag 'v3.18.49' into linux-linaro-lsk-v3.18\n\n This is the 3.18.49 stable release","distinct":true,"url":"https://api.github.com/repos/celtare21/android_kernel_leeco_msm8996/commits/5d06629e1087d28f49cc36b1a5383fd21cb1edef"},{"sha":"abac8501bf404f2aae45cd8a13f4b6522a08b8ea","author":{"name":"Alex Shi","email":"86471483ef45d8c07197ca74d2a2a81eaf9f0582@linaro.org"},"message":" Merge tag 'v3.18.50' into linux-linaro-lsk-v3.18\n\n This is the 3.18.50 stable release","distinct":true,"url":"https://api.github.com/repos/celtare21/android_kernel_leeco_msm8996/commits/abac8501bf404f2aae45cd8a13f4b6522a08b8ea"},{"sha":"a88ba91be90186debe98efcc84aa2a12b92d0fba","author":{"name":"Alex Shi","email":"86471483ef45d8c07197ca74d2a2a81eaf9f0582@linaro.org"},"message":" Merge tag 'v3.18.51' into linux-linaro-lsk-v3.18\n\n This is the 3.18.51 stable release","distinct":true,"url":"https://api.github.com/repos/celtare21/android_kernel_leeco_msm8996/commits/a88ba91be90186debe98efcc84aa2a12b92d0fba"},{"sha":"d4a181a68ad99f0a819212f9fc09690707891325","author":{"name":"Alex Shi","email":"86471483ef45d8c07197ca74d2a2a81eaf9f0582@linaro.org"},"message":"Merge remote-tracking branch 'lts/linux-3.18.y' into linux-linaro-lsk-v3.18\n\nConflicts:\n\tfix feature number error in arch/arm64/include/asm/cpufeature.h","distinct":true,"url":"https://api.github.com/repos/celtare21/android_kernel_leeco_msm8996/commits/d4a181a68ad99f0a819212f9fc09690707891325"},{"sha":"9d92a6ee405610ce9d250307d9c81807d1bdcc33","author":{"name":"Alex Shi","email":"86471483ef45d8c07197ca74d2a2a81eaf9f0582@linaro.org"},"message":" Merge tag 'v3.18.55' into linux-linaro-lsk-v3.18\n\n This is the 3.18.55 stable release","distinct":true,"url":"https://api.github.com/repos/celtare21/android_kernel_leeco_msm8996/commits/9d92a6ee405610ce9d250307d9c81807d1bdcc33"},{"sha":"d3e2269a93dfccde5e3914c587148bfb7c098922","author":{"name":"Alex Shi","email":"86471483ef45d8c07197ca74d2a2a81eaf9f0582@linaro.org"},"message":"Revert \"net: sysctl_net_core: Fix warning: 'one' defined but not used\"\n\nThis reverts commit f0387a70c1323f223343d73856ef36414c86d670.\n\nThe variable 'one' used again in 3.18-stable. so recover it for temporary\nsolution. Stable kernel should picked up for long term using.\n\nb1cb59cf2e  net: sysctl_net_core: check SNDBUF and RCVBUF for min length","distinct":true,"url":"https://api.github.com/repos/celtare21/android_kernel_leeco_msm8996/commits/d3e2269a93dfccde5e3914c587148bfb7c098922"},{"sha":"ba156556efc08b9a885bd4fd4307d95dc194b3e2","author":{"name":"Andrew Morton","email":"1c34db6615bc25a29a6a7c99217d037c3d74d16a@linux-foundation.org"},"message":"include/linux/kmemleak.h: needs slab.h\n\ninclude/linux/kmemleak.h: In function 'kmemleak_alloc_recursive':\ninclude/linux/kmemleak.h:43: error: 'SLAB_NOLEAKTRACE' undeclared (first use in this function)\n\nCc: Joonsoo Kim <iamjoonsoo.kim@lge.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\n(cherry picked from commit 66f2ca7e3f59312888131546176b42d6e248558a)\nSigned-off-by: Alex Shi <alex.shi@linaro.org>","distinct":true,"url":"https://api.github.com/repos/celtare21/android_kernel_leeco_msm8996/commits/ba156556efc08b9a885bd4fd4307d95dc194b3e2"},{"sha":"e9ab4d37b3f9e2ed46d2f14b6caceb586886898d","author":{"name":"Alex Shi","email":"86471483ef45d8c07197ca74d2a2a81eaf9f0582@linaro.org"},"message":" Merge tag 'v3.18.56' into linux-linaro-lsk-v3.18\n\n This is the 3.18.56 stable release","distinct":true,"url":"https://api.github.com/repos/celtare21/android_kernel_leeco_msm8996/commits/e9ab4d37b3f9e2ed46d2f14b6caceb586886898d"},{"sha":"720fdb6ff6a3c447b5812bb11bd3e8ed0f9e9f8d","author":{"name":"Alex Shi","email":"86471483ef45d8c07197ca74d2a2a81eaf9f0582@linaro.org"},"message":" Merge tag 'v3.18.57' into linux-linaro-lsk-v3.18\n\n This is the 3.18.57 stable release","distinct":true,"url":"https://api.github.com/repos/celtare21/android_kernel_leeco_msm8996/commits/720fdb6ff6a3c447b5812bb11bd3e8ed0f9e9f8d"},{"sha":"8f3b6ea32b7cbfe5cb79379ee30a5bc6a0efb492","author":{"name":"Amit Pundir","email":"afbf329241dfb55d52837a86a84bc563d5e8c629@linaro.org"},"message":"Merge 'linux-linaro-lsk-v3.18' into linux-linaro-lsk-v3.18-android\n\nConflicts:\n\tarch/arm/kernel/head-nommu.S\n\tarch/arm64/kernel/entry.S\n\tarch/arm64/kernel/hw_breakpoint.c\n\tarch/arm64/kernel/traps.c\n\tdrivers/media/tuners/tuner-xc2028.c\n\tdrivers/staging/android/binder.c\n\tdrivers/usb/gadget/function/u_ether.c\n\tfs/ocfs2/acl.c\n\tkernel/sched/core.c\n\tmm/memory.c\n\nAbove conflicts are resolved following android-3.18 references.\n\nSigned-off-by: Amit Pundir <amit.pundir@linaro.org>","distinct":true,"url":"https://api.github.com/repos/celtare21/android_kernel_leeco_msm8996/commits/8f3b6ea32b7cbfe5cb79379ee30a5bc6a0efb492"},{"sha":"855658b3bc9dceb85474534f9a9b6e9c5ec8134c","author":{"name":"Theodore Ts'o","email":"27d72d8f7672ec04389c6b6ff53fcc4e9145bb77@mit.edu"},"message":"UPSTREAM: ext4 crypto: add missing locking for keyring_key access\n\ncommit db7730e3091a52c2fcd8fcc952b964d88998e675 upstream.\n\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\n(cherry picked from commit b80b70ef40459ec9e7493cef5e91e4e11dad9e42)\nChange-Id: I004fd40131905f5cebe0e830c5eeedc3a3c97ba7\nSigned-off-by: Eric Biggers <ebiggers@google.com>","distinct":true,"url":"https://api.github.com/repos/celtare21/android_kernel_leeco_msm8996/commits/855658b3bc9dceb85474534f9a9b6e9c5ec8134c"},{"sha":"7a9e5208fe6b25d81327e761ace9e3d46c34825d","author":{"name":"Eric Whitney","email":"4f2966bc3dc6b1265568a0175130a75aa7c73eba@gmail.com"},"message":"UPSTREAM: ext4: enforce online defrag restriction for encrypted files\n\ncommit 14fbd4aa613bd5110556c281799ce36dc6f3ba97 upstream.\n\nOnline defragging of encrypted files is not currently implemented.\nHowever, the move extent ioctl can still return successfully when\ncalled.  For example, this occurs when xfstest ext4/020 is run on an\nencrypted file system, resulting in a corrupted test file and a\ncorresponding test failure.\n\nUntil the proper functionality is implemented, fail the move extent\nioctl if either the original or donor file is encrypted.\n\nSigned-off-by: Eric Whitney <enwlinux@gmail.com>\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\n(cherry picked from commit 76a8f17e0b850d5bb842097b0ee9c2e96af806a0)\nChange-Id: Ifaa55e8b4acc07a93a246ded4c233250cfbc2aac\nSigned-off-by: Eric Biggers <ebiggers@google.com>","distinct":true,"url":"https://api.github.com/repos/celtare21/android_kernel_leeco_msm8996/commits/7a9e5208fe6b25d81327e761ace9e3d46c34825d"},{"sha":"a090beefc4e27ac30ba790f61d7d21273f669ec1","author":{"name":"Eric Biggers","email":"0106d512ed1cb672be29d4b167a07ead51709fba@google.com"},"message":"UPSTREAM: fscrypto: add authorization check for setting encryption policy\n\ncommit 163ae1c6ad6299b19e22b4a35d5ab24a89791a98 upstream.\n\nOn an ext4 or f2fs filesystem with file encryption supported, a user\ncould set an encryption policy on any empty directory(*) to which they\nhad readonly access.  This is obviously problematic, since such a\ndirectory might be owned by another user and the new encryption policy\nwould prevent that other user from creating files in their own directory\n(for example).\n\nFix this by requiring inode_owner_or_capable() permission to set an\nencryption policy.  This means that either the caller must own the file,\nor the caller must have the capability CAP_FOWNER.\n\n(*) Or also on any regular file, for f2fs v4.6 and later and ext4\n    v4.8-rc1 and later; a separate bug fix is coming for that.\n\nSigned-off-by: Eric Biggers <ebiggers@google.com>\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\n(cherry picked from commit 8d693a2e67b5793ee58d106fded28902b7fd0f72)\nChange-Id: I4621243c8a21a25450ee06b7e64304e9cbdfae7d\nSigned-off-by: Eric Biggers <ebiggers@google.com>","distinct":true,"url":"https://api.github.com/repos/celtare21/android_kernel_leeco_msm8996/commits/a090beefc4e27ac30ba790f61d7d21273f669ec1"},{"sha":"934c4a11fb9f11f20cb1641558bbfdd922eabeb0","author":{"name":"Eric Biggers","email":"0106d512ed1cb672be29d4b167a07ead51709fba@google.com"},"message":"UPSTREAM: fscrypto: require write access to mount to set encryption policy\n\ncommit ba63f23d69a3a10e7e527a02702023da68ef8a6d upstream.\n\nSince setting an encryption policy requires writing metadata to the\nfilesystem, it should be guarded by mnt_want_write/mnt_drop_write.\nOtherwise, a user could cause a write to a frozen or readonly\nfilesystem.  This was handled correctly by f2fs but not by ext4.  Make\nfscrypt_process_policy() handle it rather than relying on the filesystem\nto get it right.\n\nSigned-off-by: Eric Biggers <ebiggers@google.com>\nCc: stable@vger.kernel.org # 4.1+; check fs/{ext4,f2fs}\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>\nAcked-by: Jaegeuk Kim <jaegeuk@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\n(cherry picked from commit bf63b9d429357bcb4857259874e36a44855f56ae)\nChange-Id: I7431967982d93a6718497892720290e71998a542\nSigned-off-by: Eric Biggers <ebiggers@google.com>","distinct":true,"url":"https://api.github.com/repos/celtare21/android_kernel_leeco_msm8996/commits/934c4a11fb9f11f20cb1641558bbfdd922eabeb0"},{"sha":"72cd0baeacd2a730f81aad141af83584b23f821c","author":{"name":"Eric Biggers","email":"0106d512ed1cb672be29d4b167a07ead51709fba@google.com"},"message":"UPSTREAM: fscrypt: fix renaming and linking special files\n\ncommit 42d97eb0ade31e1bc537d086842f5d6e766d9d51 upstream.\n\nAttempting to link a device node, named pipe, or socket file into an\nencrypted directory through rename(2) or link(2) always failed with\nEPERM.  This happened because fscrypt_has_permitted_context() saw that\nthe file was unencrypted and forbid creating the link.  This behavior\nwas unexpected because such files are never encrypted; only regular\nfiles, directories, and symlinks can be encrypted.\n\nTo fix this, make fscrypt_has_permitted_context() always return true on\nspecial files.\n\nThis will be covered by a test in my encryption xfstests patchset.\n\nFixes: 9bd8212f981e (\"ext4 crypto: add encryption policy and password salt support\")\nSigned-off-by: Eric Biggers <ebiggers@google.com>\nReviewed-by: Richard Weinberger <richard@nod.at>\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\n(cherry picked from commit fd74e8d258da9f9678da6bf88a0b02b2c1b71d0c)\nChange-Id: Iaf04528b8d4652a98072853dcb227f79ff9e263d\nSigned-off-by: Eric Biggers <ebiggers@google.com>","distinct":true,"url":"https://api.github.com/repos/celtare21/android_kernel_leeco_msm8996/commits/72cd0baeacd2a730f81aad141af83584b23f821c"},{"sha":"8cb943c75c3ee6cd30ceb406bb5b291460d997e3","author":{"name":"Eric Biggers","email":"0106d512ed1cb672be29d4b167a07ead51709fba@google.com"},"message":"UPSTREAM: fscrypto: lock inode while setting encryption policy\n\ncommit 8906a8223ad4909b391c5628f7991ebceda30e52 upstream.\n\ni_rwsem needs to be acquired while setting an encryption policy so that\nconcurrent calls to FS_IOC_SET_ENCRYPTION_POLICY are correctly\nserialized (especially the ->get_context() + ->set_context() pair), and\nso that new files cannot be created in the directory during or after the\n->empty_dir() check.\n\nSigned-off-by: Eric Biggers <ebiggers@google.com>\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>\nReviewed-by: Richard Weinberger <richard@nod.at>\nCc: stable@vger.kernel.org\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\n(cherry picked from commit 3a19419c50c6ee386ca6d22a23acc2df51583d3d)\nChange-Id: I67a50f992998f985bd0fe98245c1a2525ce5d261\nSigned-off-by: Eric Biggers <ebiggers@google.com>","distinct":true,"url":"https://api.github.com/repos/celtare21/android_kernel_leeco_msm8996/commits/8cb943c75c3ee6cd30ceb406bb5b291460d997e3"},{"sha":"b4444e44c07291d2188103e97dae82aa99ca66c4","author":{"name":"Eric Biggers","email":"0106d512ed1cb672be29d4b167a07ead51709fba@google.com"},"message":"UPSTREAM: fscrypt: remove broken support for detecting keyring key revocation\n\ncommit 1b53cf9815bb4744958d41f3795d5d5a1d365e2d upstream.\n\nFilesystem encryption ostensibly supported revoking a keyring key that\nhad been used to \"unlock\" encrypted files, causing those files to become\n\"locked\" again.  This was, however, buggy for several reasons, the most\nsevere of which was that when key revocation happened to be detected for\nan inode, its fscrypt_info was immediately freed, even while other\nthreads could be using it for encryption or decryption concurrently.\nThis could be exploited to crash the kernel or worse.\n\nThis patch fixes the use-after-free by removing the code which detects\nthe keyring key having been revoked, invalidated, or expired.  Instead,\nan encrypted inode that is \"unlocked\" now simply remains unlocked until\nit is evicted from memory.  Note that this is no worse than the case for\nblock device-level encryption, e.g. dm-crypt, and it still remains\npossible for a privileged user to evict unused pages, inodes, and\ndentries by running 'sync; echo 3 > /proc/sys/vm/drop_caches', or by\nsimply unmounting the filesystem.  In fact, one of those actions was\nalready needed anyway for key revocation to work even somewhat sanely.\nThis change is not expected to break any applications.\n\nIn the future I'd like to implement a real API for fscrypt key\nrevocation that interacts sanely with ongoing filesystem operations ---\nwaiting for existing operations to complete and blocking new operations,\nand invalidating and sanitizing key material and plaintext from the VFS\ncaches.  But this is a hard problem, and for now this bug must be fixed.\n\nThis bug affected almost all versions of ext4, f2fs, and ubifs\nencryption, and it was potentially reachable in any kernel configured\nwith encryption support (CONFIG_EXT4_ENCRYPTION=y,\nCONFIG_EXT4_FS_ENCRYPTION=y, CONFIG_F2FS_FS_ENCRYPTION=y, or\nCONFIG_UBIFS_FS_ENCRYPTION=y).  Note that older kernels did not use the\nshared fs/crypto/ code, but due to the potential security implications\nof this bug, it may still be worthwhile to backport this fix to them.\n\nFixes: b7236e21d55f (\"ext4 crypto: reorganize how we store keys in the inode\")\nSigned-off-by: Eric Biggers <ebiggers@google.com>\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>\nAcked-by: Michael Halcrow <mhalcrow@google.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\n(cherry picked from commit 7a5202190810dde1467718235c1f650fcf57592a)\nChange-Id: I5529903c0a1e499b73c1104d2b882e040f8d15fb\nSigned-off-by: Eric Biggers <ebiggers@google.com>","distinct":true,"url":"https://api.github.com/repos/celtare21/android_kernel_leeco_msm8996/commits/b4444e44c07291d2188103e97dae82aa99ca66c4"},{"sha":"fd783a2aae1c8a1d431b8a43aba63f1042227530","author":{"name":"Theodore Ts'o","email":"27d72d8f7672ec04389c6b6ff53fcc4e9145bb77@mit.edu"},"message":"UPSTREAM: ext4 crypto: revalidate dentry after adding or removing the key\n\ncommit 28b4c263961c47da84ed8b5be0b5116bad1133eb upstream.\n\nAdd a validation check for dentries for encrypted directory to make\nsure we're not caching stale data after a key has been added or removed.\n\nAlso check to make sure that status of the encryption key is updated\nwhen readdir(2) is executed.\n\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>\nSigned-off-by: Eric Biggers <ebiggers@google.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\n(cherry picked from commit 2faff9d1dfc560da3bfba6a8ab0c30246fd6c1cb)\nChange-Id: I9b77145c13b70df8dec5a90c977d6dc98d9989ae\nSigned-off-by: Eric Biggers <ebiggers@google.com>","distinct":true,"url":"https://api.github.com/repos/celtare21/android_kernel_leeco_msm8996/commits/fd783a2aae1c8a1d431b8a43aba63f1042227530"},{"sha":"edfbf0c88bb28b098b210669318e78b70bc78d42","author":{"name":"Theodore Ts'o","email":"27d72d8f7672ec04389c6b6ff53fcc4e9145bb77@mit.edu"},"message":"UPSTREAM: ext4 crypto: use dget_parent() in ext4_d_revalidate()\n\ncommit 3d43bcfef5f0548845a425365011c499875491b0 upstream.\n\nThis avoids potential problems caused by a race where the inode gets\nrenamed out from its parent directory and the parent directory is\ndeleted while ext4_d_revalidate() is running.\n\nFixes: 28b4c263961c\nReported-by: Al Viro <viro@ZenIV.linux.org.uk>\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>\nSigned-off-by: Eric Biggers <ebiggers@google.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\n(cherry picked from commit 41948f88a521b95e8abc793602015a6d45f52a06)\nChange-Id: Icea8f440a708274ecfa12d0c2a392b6aa3cc22c4\nSigned-off-by: Eric Biggers <ebiggers@google.com>","distinct":true,"url":"https://api.github.com/repos/celtare21/android_kernel_leeco_msm8996/commits/edfbf0c88bb28b098b210669318e78b70bc78d42"},{"sha":"4783ae382584b802d1274dea5a642b7ba75ad436","author":{"name":"Jaegeuk Kim","email":"c9e6543abf9bc130570115f8ac41a9d9b583b810@kernel.org"},"message":"UPSTREAM: ext4/fscrypto: avoid RCU lookup in d_revalidate\n\ncommit 03a8bb0e53d9562276045bdfcf2b5de2e4cff5a1 upstream.\n\nAs Al pointed, d_revalidate should return RCU lookup before using d_inode.\nThis was originally introduced by:\ncommit 34286d666230 (\"fs: rcu-walk aware d_revalidate method\").\n\nReported-by: Al Viro <viro@zeniv.linux.org.uk>\nSigned-off-by: Jaegeuk Kim <jaegeuk@kernel.org>\nCc: Theodore Ts'o <tytso@mit.edu>\nSigned-off-by: Eric Biggers <ebiggers@google.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\n(cherry picked from commit 16fb859f9b2bb246a18b4d0edc605774193c33b7)\nChange-Id: Ib3e41f923f02845e0ef78d65706cdc0bde30b9d9\nSigned-off-by: Eric Biggers <ebiggers@google.com>","distinct":true,"url":"https://api.github.com/repos/celtare21/android_kernel_leeco_msm8996/commits/4783ae382584b802d1274dea5a642b7ba75ad436"}]}
{"actor":{"display_login":"celtare21"}}