{"push_id":2807558696,"size":212,"distinct_size":212,"ref":"refs/heads/Caesium-Extended","head":"2c4350fbc2a240e9e68a1937a4ee8814ade1ec24","before":"b705755f362847a6cb214a9d5446cd4d6e04e5ae","commits":[{"sha":"9047851e99073a968c10e891523ae1f9cafef8ae","author":{"name":"Felipe F. Tonello","email":"608e01334f5575f10813efa40ce0102f2dc0a75e@felipetonello.com"},"message":"usb: gadget: define free_ep_req as universal function\n\ncommit 079fe5a6da616891cca1a26e803e1df2a87e9ae5 upstream.\n\nThis function is shared between gadget functions, so this avoid unnecessary\nduplicated code and potentially avoid memory leaks.\n\nReviewed-by: Robert Baldyga <r.baldyga@samsung.com>\nSigned-off-by: Felipe F. Tonello <eu@felipetonello.com>\nSigned-off-by: Felipe Balbi <balbi@ti.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/TR-OS/OP3-Kernel/commits/9047851e99073a968c10e891523ae1f9cafef8ae"},{"sha":"419eaaaba12ccb371108e816fcd1efc4230d6a60","author":{"name":"Mel Gorman","email":"39ea6a09710987173e32e37c86918024a0f441c1@suse.de"},"message":"futex: Remove requirement for lock_page() in get_futex_key()\n\ncommit 65d8fc777f6dcfee12785c057a6b57f679641c90 upstream.\n\nWhen dealing with key handling for shared futexes, we can drastically reduce\nthe usage/need of the page lock. 1) For anonymous pages, the associated futex\nobject is the mm_struct which does not require the page lock. 2) For inode\nbased, keys, we can check under RCU read lock if the page mapping is still\nvalid and take reference to the inode. This just leaves one rare race that\nrequires the page lock in the slow path when examining the swapcache.\n\nAdditionally realtime users currently have a problem with the page lock being\ncontended for unbounded periods of time during futex operations.\n\nTask A\n     get_futex_key()\n     lock_page()\n    ---> preempted\n\nNow any other task trying to lock that page will have to wait until\ntask A gets scheduled back in, which is an unbound time.\n\nWith this patch, we pretty much have a lockless futex_get_key().\n\nExperiments show that this patch can boost/speedup the hashing of shared\nfutexes with the perf futex benchmarks (which is good for measuring such\nchange) by up to 45% when there are high (> 100) thread counts on a 60 core\nWestmere. Lower counts are pretty much in the noise range or less than 10%,\nbut mid range can be seen at over 30% overall throughput (hash ops/sec).\nThis makes anon-mem shared futexes much closer to its private counterpart.\n\nSigned-off-by: Mel Gorman <mgorman@suse.de>\n[ Ported on top of thp refcount rework, changelog, comments, fixes. ]\nSigned-off-by: Davidlohr Bueso <dbueso@suse.de>\nReviewed-by: Thomas Gleixner <tglx@linutronix.de>\nCc: Chris Mason <clm@fb.com>\nCc: Darren Hart <dvhart@linux.intel.com>\nCc: Hugh Dickins <hughd@google.com>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Mel Gorman <mgorman@techsingularity.net>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>\nCc: dave@stgolabs.net\nLink: http://lkml.kernel.org/r/1455045314-8305-3-git-send-email-dave@stgolabs.net\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\nSigned-off-by: Chenbo Feng <fengc@google.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/TR-OS/OP3-Kernel/commits/419eaaaba12ccb371108e816fcd1efc4230d6a60"},{"sha":"dbfceec3b091acb5a711e6e752fa660ef3e105e0","author":{"name":"Krzysztof Opasiak","email":"4c491ef279967ee84b1d28e44f3e74be7a08ac30@gmail.com"},"message":"usb: gadget: f_hid: fix: Prevent accessing released memory\n\ncommit aa65d11aa008f4de58a9cee7e121666d9d68505e upstream.\n\nWhen we unlock our spinlock to copy data to user we may get\ndisabled by USB host and free the whole list of completed out\nrequests including the one from which we are copying the data\nto user memory.\n\nTo prevent from this let's remove our working element from\nthe list and place it back only if there is sth left when we\nfinish with it.\n\nFixes: 99c515005857 (\"usb: gadget: hidg: register OUT INT endpoint for SET_REPORT\")\nCc: stable@vger.kernel.org\nTested-by: David Lechner <david@lechnology.com>\nSigned-off-by: Krzysztof Opasiak <k.opasiak@samsung.com>\nSigned-off-by: Felipe Balbi <felipe.balbi@linux.intel.com>\nCc: Jerry Zhang <zhangjerry@google.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/TR-OS/OP3-Kernel/commits/dbfceec3b091acb5a711e6e752fa660ef3e105e0"},{"sha":"41f3d42943228c851c8e80ef781dca77722dc1e5","author":{"name":"Li Jinyue","email":"45c85f10674f4db47cce26d34d806709a7722127@huawei.com"},"message":"futex: Prevent overflow by strengthen input validation\n\ncommit fbe0e839d1e22d88810f3ee3e2f1479be4c0aa4a upstream.\n\nUBSAN reports signed integer overflow in kernel/futex.c:\n\n UBSAN: Undefined behaviour in kernel/futex.c:2041:18\n signed integer overflow:\n 0 - -2147483648 cannot be represented in type 'int'\n\nAdd a sanity check to catch negative values of nr_wake and nr_requeue.\n\nSigned-off-by: Li Jinyue <lijinyue@huawei.com>\nSigned-off-by: Thomas Gleixner <tglx@linutronix.de>\nCc: peterz@infradead.org\nCc: dvhart@infradead.org\nLink: https://lkml.kernel.org/r/1513242294-31786-1-git-send-email-lijinyue@huawei.com\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/TR-OS/OP3-Kernel/commits/41f3d42943228c851c8e80ef781dca77722dc1e5"},{"sha":"f7e1ad5249e71099796929e41277c81b3e161699","author":{"name":"Johannes Thumshirn","email":"76e27a2cf2160151c27b307564ef391a743f57c5@suse.de"},"message":"scsi: sg: don't return bogus Sg_requests\n\ncommit 48ae8484e9fc324b4968d33c585e54bc98e44d61 upstream.\n\nIf the list search in sg_get_rq_mark() fails to find a valid request, we\nreturn a bogus element. This then can later lead to a GPF in\nsg_remove_scat().\n\nSo don't return bogus Sg_requests in sg_get_rq_mark() but NULL in case\nthe list search doesn't find a valid request.\n\nSigned-off-by: Johannes Thumshirn <jthumshirn@suse.de>\nReported-by: Andrey Konovalov <andreyknvl@google.com>\nCc: Hannes Reinecke <hare@suse.de>\nCc: Christoph Hellwig <hch@lst.de>\nCc: Doug Gilbert <dgilbert@interlog.com>\nReviewed-by: Hannes Reinecke <hare@suse.de>\nAcked-by: Doug Gilbert <dgilbert@interlog.com>\nSigned-off-by: Martin K. Petersen <martin.petersen@oracle.com>\nCc: Tony Battersby <tonyb@cybernetics.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/TR-OS/OP3-Kernel/commits/f7e1ad5249e71099796929e41277c81b3e161699"},{"sha":"30c0651aefe47e9cdc019639754927018a5c1f4b","author":{"name":"Seunghun Han","email":"86b41029b346199b31f90756f7538c26f14afbdf@gmail.com"},"message":"x86/MCE: Serialize sysfs changes\n\ncommit b3b7c4795ccab5be71f080774c45bbbcc75c2aaf upstream.\n\nThe check_interval file in\n\n  /sys/devices/system/machinecheck/machinecheck<cpu number>\n\ndirectory is a global timer value for MCE polling. If it is changed by one\nCPU, mce_restart() broadcasts the event to other CPUs to delete and restart\nthe MCE polling timer and __mcheck_cpu_init_timer() reinitializes the\nmce_timer variable.\n\nIf more than one CPU writes a specific value to the check_interval file\nconcurrently, mce_timer is not protected from such concurrent accesses and\nall kinds of explosions happen. Since only root can write to those sysfs\nvariables, the issue is not a big deal security-wise.\n\nHowever, concurrent writes to these configuration variables is void of\nreason so the proper thing to do is to serialize the access with a mutex.\n\nBoris:\n\n - Make store_int_with_restart() use device_store_ulong() to filter out\n   negative intervals\n - Limit min interval to 1 second\n - Correct locking\n - Massage commit message\n\nSigned-off-by: Seunghun Han <kkamagui@gmail.com>\nSigned-off-by: Borislav Petkov <bp@suse.de>\nSigned-off-by: Thomas Gleixner <tglx@linutronix.de>\nCc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nCc: Tony Luck <tony.luck@intel.com>\nCc: linux-edac <linux-edac@vger.kernel.org>\nCc: stable@vger.kernel.org\nLink: http://lkml.kernel.org/r/20180302202706.9434-1-kkamagui@gmail.com\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/TR-OS/OP3-Kernel/commits/30c0651aefe47e9cdc019639754927018a5c1f4b"},{"sha":"7209c35c81a3a5eb709517131f349c3b0d6e259e","author":{"name":"Daniel Rosenberg","email":"b28fe47f344ea47a742972f6caa7ef1537d21708@google.com"},"message":"ANDROID: sdcardfs: Check stacked filesystem depth\n\nbug: 111860541\nChange-Id: Ia0a30b2b8956c4ada28981584cd8647713a1e993\nSigned-off-by: Daniel Rosenberg <drosen@google.com>\nSigned-off-by: Harsh Shandilya <harsh@prjkt.io>","distinct":true,"url":"https://api.github.com/repos/TR-OS/OP3-Kernel/commits/7209c35c81a3a5eb709517131f349c3b0d6e259e"},{"sha":"4ff5896bdc9451fd4136a69cd20bf612c5287f04","author":{"name":"Eric Biggers","email":"6f6115196800bbe9712b3f04c7e40093bb382fc5@google.com"},"message":"fscrypt: use unbound workqueue for decryption\n\nImprove fscrypt read performance by switching the decryption workqueue\nfrom bound to unbound.  With the bound workqueue, when multiple bios\ncompleted on the same CPU, they were decrypted on that same CPU.  But\nwith the unbound queue, they are now decrypted in parallel on any CPU.\n\nAlthough fscrypt read performance can be tough to measure due to the\nmany sources of variation, this change is most beneficial when\ndecryption is slow, e.g. on CPUs without AES instructions.  For example,\nI timed tarring up encrypted directories on f2fs.  On x86 with AES-NI\ninstructions disabled, the unbound workqueue improved performance by\nabout 25-35%, using 1 to NUM_CPUs jobs with 4 or 8 CPUs available.  But\nwith AES-NI enabled, performance was unchanged to within ~2%.\n\nI also did the same test on a quad-core ARM CPU using xts-speck128-neon\nencryption.  There performance was usually about 10% better with the\nunbound workqueue, bringing it closer to the unencrypted speed.\n\nThe unbound workqueue may be worse in some cases due to worse locality,\nbut I think it's still the better default.  dm-crypt uses an unbound\nworkqueue by default too, so this change makes fscrypt match.\n\nSigned-off-by: Eric Biggers <ebiggers@google.com>\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>\nSigned-off-by: Harsh Shandilya <harsh@prjkt.io>","distinct":true,"url":"https://api.github.com/repos/TR-OS/OP3-Kernel/commits/4ff5896bdc9451fd4136a69cd20bf612c5287f04"},{"sha":"7711667537fa768bb8112ebbdca80dcad011e0d0","author":{"name":"Eric Biggers","email":"6f6115196800bbe9712b3f04c7e40093bb382fc5@google.com"},"message":"fscrypt: clean up after fscrypt_prepare_lookup() conversions\n\nNow that all filesystems have been converted to use\nfscrypt_prepare_lookup(), we can remove the fscrypt_set_d_op() and\nfscrypt_set_encrypted_dentry() functions as well as un-export\nfscrypt_d_ops.\n\nSigned-off-by: Eric Biggers <ebiggers@google.com>\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>\nSigned-off-by: Harsh Shandilya <harsh@prjkt.io>","distinct":true,"url":"https://api.github.com/repos/TR-OS/OP3-Kernel/commits/7711667537fa768bb8112ebbdca80dcad011e0d0"},{"sha":"fdac36e0d66cfdd9ecf8ebb4d8541af77c95c277","author":{"name":"Eric Biggers","email":"6f6115196800bbe9712b3f04c7e40093bb382fc5@google.com"},"message":"fscrypt: remove unnecessary NULL check when allocating skcipher\n\ncrypto_alloc_skcipher() returns an ERR_PTR() on failure, not NULL.\nRemove the unnecessary check for NULL.\n\nSigned-off-by: Eric Biggers <ebiggers@google.com>\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>\nSigned-off-by: Harsh Shandilya <harsh@prjkt.io>","distinct":true,"url":"https://api.github.com/repos/TR-OS/OP3-Kernel/commits/fdac36e0d66cfdd9ecf8ebb4d8541af77c95c277"},{"sha":"7cf5b726b3c8d0413a2db4c05d7328b25f117ea5","author":{"name":"Eric Biggers","email":"6f6115196800bbe9712b3f04c7e40093bb382fc5@google.com"},"message":"fscrypt: remove error messages for skcipher_request_alloc() failure\n\nskcipher_request_alloc() can only fail due to lack of memory, and in\nthat case the memory allocator will have already printed a detailed\nerror message.  Thus, remove the redundant error messages from fscrypt.\n\nSigned-off-by: Eric Biggers <ebiggers@google.com>\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>\nSigned-off-by: Harsh Shandilya <harsh@prjkt.io>","distinct":true,"url":"https://api.github.com/repos/TR-OS/OP3-Kernel/commits/7cf5b726b3c8d0413a2db4c05d7328b25f117ea5"},{"sha":"7d5b77b412d1b5fc5f2de30c42d8a041118061f5","author":{"name":"Eric Biggers","email":"6f6115196800bbe9712b3f04c7e40093bb382fc5@google.com"},"message":"fscrypt: remove stale comment from fscrypt_d_revalidate()\n\nSigned-off-by: Eric Biggers <ebiggers@google.com>\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>\nSigned-off-by: Harsh Shandilya <harsh@prjkt.io>","distinct":true,"url":"https://api.github.com/repos/TR-OS/OP3-Kernel/commits/7d5b77b412d1b5fc5f2de30c42d8a041118061f5"},{"sha":"392fcd5d3dba7413e0e395cdaca3e3877985f6aa","author":{"name":"Eric Biggers","email":"6f6115196800bbe9712b3f04c7e40093bb382fc5@google.com"},"message":"fscrypt: don't clear flags on crypto transform\n\nfscrypt is clearing the flags on the crypto_skcipher it allocates for\neach inode.  But, this is unnecessary and may cause problems in the\nfuture because it will even clear flags that are meant to be internal to\nthe crypto API, e.g. CRYPTO_TFM_NEED_KEY.\n\nRemove the unnecessary flag clearing.\n\nSigned-off-by: Eric Biggers <ebiggers@google.com>\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>\nSigned-off-by: Harsh Shandilya <harsh@prjkt.io>","distinct":true,"url":"https://api.github.com/repos/TR-OS/OP3-Kernel/commits/392fcd5d3dba7413e0e395cdaca3e3877985f6aa"},{"sha":"45cd33aeffcdfc77886f7c625bb2d3dde36b0db2","author":{"name":"Eric Biggers","email":"6f6115196800bbe9712b3f04c7e40093bb382fc5@google.com"},"message":"fscrypt: don't special-case EOPNOTSUPP from fscrypt_get_encryption_info()\n\nIn fscrypt_setup_filename(), remove the unnecessary check for\nfscrypt_get_encryption_info() returning EOPNOTSUPP.  There's no reason\nto handle this error differently from any other.  I think there may have\nbeen some confusion because the \"notsupp\" version of\nfscrypt_get_encryption_info() returns EOPNOTSUPP -- but that's not\napplicable from inside fs/crypto/.\n\nSigned-off-by: Eric Biggers <ebiggers@google.com>\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>\nSigned-off-by: Harsh Shandilya <harsh@prjkt.io>","distinct":true,"url":"https://api.github.com/repos/TR-OS/OP3-Kernel/commits/45cd33aeffcdfc77886f7c625bb2d3dde36b0db2"},{"sha":"95f44c9b2b47163e37c3112adf7b7a3633c73e55","author":{"name":"Eric Biggers","email":"6f6115196800bbe9712b3f04c7e40093bb382fc5@google.com"},"message":"fscrypt: drop max_namelen check from fname_decrypt()\n\nfname_decrypt() returns an error if the input filename is longer than\nthe inode's ->max_namelen() as given by the filesystem.  But, this\ndoesn't actually make sense because the filesystem provided the input\nfilename in the first place, where it was subject to the filesystem's\nlimits.  And fname_decrypt() has no internal limit itself.\n\nThus, remove this unnecessary check.\n\nSigned-off-by: Eric Biggers <ebiggers@google.com>\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>\nSigned-off-by: Harsh Shandilya <harsh@prjkt.io>","distinct":true,"url":"https://api.github.com/repos/TR-OS/OP3-Kernel/commits/95f44c9b2b47163e37c3112adf7b7a3633c73e55"},{"sha":"b89f5214ec39d607abc4252f4fcd0e7f77de37a3","author":{"name":"Eric Biggers","email":"6f6115196800bbe9712b3f04c7e40093bb382fc5@google.com"},"message":"fscrypt: drop empty name check from fname_decrypt()\n\nfname_decrypt() is validating that the encrypted filename is nonempty.\nHowever, earlier a stronger precondition was already enforced: the\nencrypted filename must be at least 16 (FS_CRYPTO_BLOCK_SIZE) bytes.\n\nDrop the redundant check for an empty filename.\n\nSigned-off-by: Eric Biggers <ebiggers@google.com>\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>\nSigned-off-by: Harsh Shandilya <harsh@prjkt.io>","distinct":true,"url":"https://api.github.com/repos/TR-OS/OP3-Kernel/commits/b89f5214ec39d607abc4252f4fcd0e7f77de37a3"},{"sha":"424af6f42a84d68adfe6e3f7ccf6a3aa63a619fb","author":{"name":"Eric Biggers","email":"6f6115196800bbe9712b3f04c7e40093bb382fc5@google.com"},"message":"fscrypt: make fscrypt_operations.max_namelen an integer\n\nNow ->max_namelen() is only called to limit the filename length when\nadding NUL padding, and only for real filenames -- not symlink targets.\nIt also didn't give the correct length for symlink targets anyway since\nit forgot to subtract 'sizeof(struct fscrypt_symlink_data)'.\n\nThus, change ->max_namelen from a function to a simple 'unsigned int'\nthat gives the filesystem's maximum filename length.\n\nSigned-off-by: Eric Biggers <ebiggers@google.com>\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>\nSigned-off-by: Harsh Shandilya <harsh@prjkt.io>","distinct":true,"url":"https://api.github.com/repos/TR-OS/OP3-Kernel/commits/424af6f42a84d68adfe6e3f7ccf6a3aa63a619fb"},{"sha":"a6b7044cd58571cd9651f0bb19aed6311a2fce37","author":{"name":"Eric Biggers","email":"6f6115196800bbe9712b3f04c7e40093bb382fc5@google.com"},"message":"fscrypt: remove unnecessary check for non-logon key type\n\nWe're passing 'key_type_logon' to request_key(), so the found key is\nguaranteed to be of type \"logon\".  Thus, there is no reason to check\nlater that the key is really a \"logon\" key.\n\nSigned-off-by: Eric Biggers <ebiggers@google.com>\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>\nSigned-off-by: Harsh Shandilya <harsh@prjkt.io>","distinct":true,"url":"https://api.github.com/repos/TR-OS/OP3-Kernel/commits/a6b7044cd58571cd9651f0bb19aed6311a2fce37"},{"sha":"8db68a845adf74ae95730ddeab74ed03e5deac3e","author":{"name":"Eric Biggers","email":"6f6115196800bbe9712b3f04c7e40093bb382fc5@google.com"},"message":"fscrypt: remove internal key size constants\n\nWith one exception, the internal key size constants such as\nFS_AES_256_XTS_KEY_SIZE are only used for the 'available_modes' array,\nwhere they really only serve to obfuscate what the values are.  Also\nsome of the constants are unused, and the key sizes tend to be in the\nnames of the algorithms anyway.  In the past these values were also\nmisused, e.g. we used to have FS_AES_256_XTS_KEY_SIZE in places that\ntechnically should have been FS_MAX_KEY_SIZE.\n\nThe exception is that FS_AES_128_ECB_KEY_SIZE is used for key\nderivation.  But it's more appropriate to use\nFS_KEY_DERIVATION_NONCE_SIZE for that instead.\n\nThus, just put the sizes directly in the 'available_modes' array.\n\nSigned-off-by: Eric Biggers <ebiggers@google.com>\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>\nSigned-off-by: Harsh Shandilya <harsh@prjkt.io>","distinct":true,"url":"https://api.github.com/repos/TR-OS/OP3-Kernel/commits/8db68a845adf74ae95730ddeab74ed03e5deac3e"},{"sha":"fb491337ba93a46d4008327c91ccd24e9b88d206","author":{"name":"Eric Biggers","email":"6f6115196800bbe9712b3f04c7e40093bb382fc5@google.com"},"message":"fscrypt: use a common logging function\n\nUse a common function for fscrypt warning and error messages so that all\nthe messages are consistently ratelimited, include the \"fscrypt:\"\nprefix, and include the filesystem name if applicable.\n\nAlso fix up a few of the log messages to be more descriptive.\n\nSigned-off-by: Eric Biggers <ebiggers@google.com>\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>\nSigned-off-by: Harsh Shandilya <harsh@prjkt.io>","distinct":true,"url":"https://api.github.com/repos/TR-OS/OP3-Kernel/commits/fb491337ba93a46d4008327c91ccd24e9b88d206"}]}
{"actor":{"display_login":"TR-OS"}}