{"push_id":1895187313,"size":55,"distinct_size":55,"ref":"refs/heads/cm-14-cust","head":"ca9c5edbc9080ba25b36ca5deddb5c846d9a162d","before":"a4bdec82394c0466bb05a3523f3fc541fa1caca2","commits":[{"sha":"6ceb4a994275d2b0d64eef0c2c86d5efe0c7437c","author":{"name":"Dinesh K Garg","email":"0ee15ef076350c4b0fc4c82bec1558f3334e6cb0@codeaurora.org"},"message":"Request based dm-crypt\n\ndm-crypt provides bios based device mapper module. dm-crypt\noperates on packets with 512 bytes size which is not effiicent\nway for HW based crypto blocks. dm-req-crypt is developed to\naddress this. dm-req-crypt works on requests which carry upto\n512KB of data for unmerged requests.\n\nChange-Id: I479230b2f0c1ab2e2a1ddb84947ebaf0629dff8c\nSigned-off-by: Dinesh K Garg <dineshg@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/csendre/android_kernel_samsung_msm8930-common/commits/6ceb4a994275d2b0d64eef0c2c86d5efe0c7437c"},{"sha":"95dba340b5757d7d694837abc7fafc56306e1fa6","author":{"name":"Dinesh K Garg","email":"0ee15ef076350c4b0fc4c82bec1558f3334e6cb0@codeaurora.org"},"message":"dm: updating crypto algorithm used by dm-req-crypt\n\ndm-req-crypt uses AES-XTS algorithm implemented by HW crypto\nengine. Crypto driver renamed the aes-xts algorithm to avoid\nconflict with SW based implementation of AES-XTS. dm-req-crypt\nmust use the new name for AES-XTS provided by crypto driver.\n\nChange-Id: I286b6435af33fd64673c7c1af4bb2447f3115868\nSigned-off-by: Dinesh K Garg <dineshg@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/csendre/android_kernel_samsung_msm8930-common/commits/95dba340b5757d7d694837abc7fafc56306e1fa6"},{"sha":"22dbdcf852646045e58faa648158574108fe1bf6","author":{"name":"Dinesh K Garg","email":"0ee15ef076350c4b0fc4c82bec1558f3334e6cb0@codeaurora.org"},"message":"dm: Adding support of AES 256 bits in dm-req-crypt\n\ndm-req-crypt currently uses AES 128 bit. Updating dm-req-crypt\nto use AES 256 bit instead.\n\nChange-Id: I2e8a4484b25496d53f1f9aa83ec6c0ed7b947901\nSigned-off-by: Dinesh K Garg <dineshg@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/csendre/android_kernel_samsung_msm8930-common/commits/22dbdcf852646045e58faa648158574108fe1bf6"},{"sha":"cdaf2f3d384b320f4d28c03d15ea8e5b99c35c93","author":{"name":"Dinesh K Garg","email":"0ee15ef076350c4b0fc4c82bec1558f3334e6cb0@codeaurora.org"},"message":"dm: Clean up dm-req-crypt\n\ndm-req-crypt defines optional functions from device mapper. These\nfunctions are not required for dm-req-crypt. dm-req-crypt has few\nmemory de-allocation issues. This change removes unnecessary\nfunctions and fixes memory deallocation issues as well.\n\nChange-Id: Id36bd13989940ce41571a8a10277730048df6f6d\nSigned-off-by: Dinesh K Garg <dineshg@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/csendre/android_kernel_samsung_msm8930-common/commits/cdaf2f3d384b320f4d28c03d15ea8e5b99c35c93"},{"sha":"8864bb48e67e61479ac80693a0c4d2ddabcdb516","author":{"name":"Dinesh K Garg","email":"0ee15ef076350c4b0fc4c82bec1558f3334e6cb0@codeaurora.org"},"message":"Setting correct HW crypto driver instance for FDE\n\nHW crypto provides different instance for different use cases.\nDm-req-crypt should use the one for full disk encryption use case.\n\nChange-Id: I22d3f6ab1dd6f83b0d5b83a681236719e2340934\nSigned-off-by: Dinesh K Garg <dineshg@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/csendre/android_kernel_samsung_msm8930-common/commits/8864bb48e67e61479ac80693a0c4d2ddabcdb516"},{"sha":"fd0b23adceec7eb4bfe49983b475a88838899056","author":{"name":"Amir Samuelov","email":"a3851d8aa26d0044b92914044d81e0b83564d157@codeaurora.org"},"message":"dm: dm-req-crypt: add support for Per-File-Encryption\n\nSupport Per-File-Encryption (PFE) based on file tagging.\nThe Per-File-Tagger (PFT) reports if a file should be encrypted or not.\nThe Per-File-Encryption can be used after Full-Disk-Encryption (FDE) was\ncompleted or without FDE.\nThe PFE and FDE uses different keys, which are managed by the Trust-Zone.\n\nChange-Id: I727ef11e252649f895a5e3f8a49ca848cea50795\nSigned-off-by: Amir Samuelov <amirs@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/csendre/android_kernel_samsung_msm8930-common/commits/fd0b23adceec7eb4bfe49983b475a88838899056"},{"sha":"dee5593106b18e50755927854c1e595382742fb9","author":{"name":"Amir Samuelov","email":"a3851d8aa26d0044b92914044d81e0b83564d157@codeaurora.org"},"message":"platform: msm: add Per-File-Tagger (PFT) driver\n\nThis driver is part of the Per-File-Encryption (PFE) feature.\nIt allows to tag enterprise files and encrypt them\nwhile keeping the user private files untagged and plain text.\n\nChange-Id: I2ba8bffb2a8815991dc3994a1f94a0c52b937a25\nSigned-off-by: Nir Ofry <nofry@codeaurora.org>\nSigned-off-by: Amir Samuelov <amirs@codeaurora.org>\n\nConflicts:\n\tdrivers/platform/msm/Kconfig\n\tdrivers/platform/msm/Makefile\n\tinclude/linux/Kbuild\n\nChange-Id: Id791f57f5a46f3393069c3cfb38d31c43c647f17","distinct":true,"url":"https://api.github.com/repos/csendre/android_kernel_samsung_msm8930-common/commits/dee5593106b18e50755927854c1e595382742fb9"},{"sha":"20f89ffef4017a8aefbd2b69e055350dfd8d67b2","author":{"name":"Amir Samuelov","email":"a3851d8aa26d0044b92914044d81e0b83564d157@codeaurora.org"},"message":"platform: msm: pft: fix close all encrypted files\n\nfilp_close() eventually calls pft_file_close().\nSimplify pft_close_opened_enc_files() and remove having mutex\nin both places that cause a deadlock.\n\nChange-Id: I0afa2d2f0806f18d430c027601fb9974855ef185\nSigned-off-by: Amir Samuelov <amirs@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/csendre/android_kernel_samsung_msm8930-common/commits/20f89ffef4017a8aefbd2b69e055350dfd8d67b2"},{"sha":"a63ac509faf8f35319709c3b5b28398431fb9d62","author":{"name":"Amir Samuelov","email":"a3851d8aa26d0044b92914044d81e0b83564d157@codeaurora.org"},"message":"platform: msm: fix PFT char device major number\n\nDynamically allocate the major number\nof the PFT character device.\n\nChange-Id: I7877579781353203753f86a3993bc5731307db2a\nSigned-off-by: Amir Samuelov <amirs@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/csendre/android_kernel_samsung_msm8930-common/commits/a63ac509faf8f35319709c3b5b28398431fb9d62"},{"sha":"ccb8c8a3e3b2f8cf2889c276b7ebbe69d0a4df05","author":{"name":"Amir Samuelov","email":"a3851d8aa26d0044b92914044d81e0b83564d157@codeaurora.org"},"message":"msm: cleanup and minor fixes for PFT driver\n\nremove unused symlink hook.\nfree open-file-list on driver exit.\ncheck return value of pft_add_file().\n\nChange-Id: Ida1e4351742ae62cafb2ffa49727f490709351e2\nSigned-off-by: Amir Samuelov <amirs@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/csendre/android_kernel_samsung_msm8930-common/commits/ccb8c8a3e3b2f8cf2889c276b7ebbe69d0a4df05"},{"sha":"9d67c79c9e90b89fe2c40a8a75ac2f862b13d110","author":{"name":"Amir Samuelov","email":"a3851d8aa26d0044b92914044d81e0b83564d157@codeaurora.org"},"message":"platform: msm: fix PFT when using direct-io\n\nWhen we read/write a file using dircet-io (O_DIRECT),\nwe can't get the inode from a bio by walking the path\nbio->bi_io_vec->bv_page->mapping->host\nsince the page is anonymous and not mapped.\nOn the other more typical cases when not using O_DIRECT,\nthe page cache is used and the bv_page is available.\n\nChange-Id: I349cad54a978ed9919f960d55f0f95c1e53262e5\nSigned-off-by: Amir Samuelov <amirs@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/csendre/android_kernel_samsung_msm8930-common/commits/9d67c79c9e90b89fe2c40a8a75ac2f862b13d110"},{"sha":"72574d1d1c7438e82207bf876256f9b1f65466ed","author":{"name":"Peter Zijlstra","email":"4d3106856cce90e8f40acc5180f60ddda3a23b6e@infradead.org"},"message":"perf: Tighten (and fix) the grouping condition\n\nThe fix from 9fc81d87420d (\"perf: Fix events installation during\nmoving group\") was incomplete in that it failed to recognise that\ncreating a group with events for different CPUs is semantically\nbroken -- they cannot be co-scheduled.\n\nFurthermore, it leads to real breakage where, when we create an event\nfor CPU Y and then migrate it to form a group on CPU X, the code gets\nconfused where the counter is programmed -- triggered in practice\nas well by me via the perf fuzzer.\n\nFix this by tightening the rules for creating groups. Only allow\ngrouping of counters that can be co-scheduled in the same context.\nThis means for the same task and/or the same cpu.\n\nChange-Id: I01d7b24b44fff039e72c80cca7f70158fa354470\nFixes: 9fc81d87420d (\"perf: Fix events installation during moving group\")\nSigned-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>\nCc: Arnaldo Carvalho de Melo <acme@kernel.org>\nCc: Jiri Olsa <jolsa@redhat.com>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nLink: http://lkml.kernel.org/r/20150123125834.090683288@infradead.org\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\nSigned-off-by: Kamal Mostafa <kamal@canonical.com>\nGit-commit: c3c87e770458aa004bd7ed3f29945ff436fd6511\nGit-repo: http://git.kernel.org/cgit/linux/kernel/git/tip/tip.git\nSigned-off-by: Patrick Fay <pfay@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/csendre/android_kernel_samsung_msm8930-common/commits/72574d1d1c7438e82207bf876256f9b1f65466ed"},{"sha":"41c0b7ba724b712ef90bc025c3f25579fe2cbeeb","author":{"name":"Zhen Kong","email":"b999fb1d59364862997bac94d5b793be36d63b01@codeaurora.org"},"message":"crypto: msm: check length before copying to buf in _debug_stats_read\n\nMake sure that `len` is not larger than `count` before copying data\nto userspace `buf` in _debug_stats_read().\n\nChange-Id: Iafb7cfa3828653f8c28183c812797c3d9a183da1\nSigned-off-by: Zhen Kong <zkong@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/csendre/android_kernel_samsung_msm8930-common/commits/41c0b7ba724b712ef90bc025c3f25579fe2cbeeb"},{"sha":"c2d68705f86995eb6dd56c677a18f015c4f18fd9","author":{"name":"Hugh Dickins","email":"11bd16bbccd141ee47d9426ad06afbc74b915cf0@google.com"},"message":"mm: fix warning in __set_page_dirty_nobuffers\n\nNew tmpfs use of !PageUptodate pages for fallocate() is triggering the\nWARNING: at mm/page-writeback.c:1990 when __set_page_dirty_nobuffers()\nis called from migrate_page_copy() for compaction.\n\nIt is anomalous that migration should use __set_page_dirty_nobuffers()\non an address_space that does not participate in dirty and writeback\naccounting; and this has also been observed to insert surprising dirty\ntags into a tmpfs radix_tree, despite tmpfs not using tags at all.\n\nWe should probably give migrate_page_copy() a better way to preserve the\ntag and migrate accounting info, when mapping_cap_account_dirty().  But\nthat needs some more work: so in the interim, avoid the warning by using\na simple SetPageDirty on PageSwapBacked pages.\n\nChange-Id: I3cc9b67912e3aaaf6849a6681c48d17756575c7e\nReported-and-tested-by: Dave Jones <davej@redhat.com>\nSigned-off-by: Hugh Dickins <hughd@google.com>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>","distinct":true,"url":"https://api.github.com/repos/csendre/android_kernel_samsung_msm8930-common/commits/c2d68705f86995eb6dd56c677a18f015c4f18fd9"},{"sha":"8f6212997e5889cc91b722fcb613536dbbd59d80","author":{"name":"Hugh Dickins","email":"11bd16bbccd141ee47d9426ad06afbc74b915cf0@google.com"},"message":"mm: migrate dirty page without clear_page_dirty_for_io etc\n\ncommit 42cb14b110a5698ccf26ce59c4441722605a3743 upstream.\n\nclear_page_dirty_for_io() has accumulated writeback and memcg subtleties\nsince v2.6.16 first introduced page migration; and the set_page_dirty()\nwhich completed its migration of PageDirty, later had to be moderated to\n__set_page_dirty_nobuffers(); then PageSwapBacked had to skip that too.\n\nNo actual problems seen with this procedure recently, but if you look into\nwhat the clear_page_dirty_for_io(page)+set_page_dirty(newpage) is actually\nachieving, it turns out to be nothing more than moving the PageDirty flag,\nand its NR_FILE_DIRTY stat from one zone to another.\n\nIt would be good to avoid a pile of irrelevant decrementations and\nincrementations, and improper event counting, and unnecessary descent of\nthe radix_tree under tree_lock (to set the PAGECACHE_TAG_DIRTY which\nradix_tree_replace_slot() left in place anyway).\n\nDo the NR_FILE_DIRTY movement, like the other stats movements, while\ninterrupts still disabled in migrate_page_move_mapping(); and don't even\nbother if the zone is the same.  Do the PageDirty movement there under\ntree_lock too, where old page is frozen and newpage not yet visible:\nbearing in mind that as soon as newpage becomes visible in radix_tree, an\nun-page-locked set_page_dirty() might interfere (or perhaps that's just\nnot possible: anything doing so should already hold an additional\nreference to the old page, preventing its migration; but play safe).\n\nBut we do still need to transfer PageDirty in migrate_page_copy(), for\nthose who don't go the mapping route through migrate_page_move_mapping().\n\nCVE-2016-3070\n\nSigned-off-by: Hugh Dickins <hughd@google.com>\nCc: Christoph Lameter <cl@linux.com>\nCc: \"Kirill A. Shutemov\" <kirill.shutemov@linux.intel.com>\nCc: Rik van Riel <riel@redhat.com>\nCc: Vlastimil Babka <vbabka@suse.cz>\nCc: Davidlohr Bueso <dave@stgolabs.net>\nCc: Oleg Nesterov <oleg@redhat.com>\nCc: Sasha Levin <sasha.levin@oracle.com>\nCc: Dmitry Vyukov <dvyukov@google.com>\nCc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\n[ciwillia@brocade.com: backported to 3.10: adjusted context]\nSigned-off-by: Charles (Chas) Williams <ciwillia@brocade.com>\nSigned-off-by: Willy Tarreau <w@1wt.eu>\n\nChange-Id: Ifee7c4f76e277763ef2dd63c810590cd237575a4","distinct":true,"url":"https://api.github.com/repos/csendre/android_kernel_samsung_msm8930-common/commits/8f6212997e5889cc91b722fcb613536dbbd59d80"},{"sha":"40be7029107198e5e862b90d32460dcb9282a551","author":{"name":"Oliver Neukum","email":"af55dedc0d50bd691239218b486da844e4a16906@suse.com"},"message":"USB: cypress_m8: add endpoint sanity check\n\nAn attack using missing endpoints exists.\n\nCVE-2016-3137\n\nChange-Id: I5a0e37bb4040d9022d784d81b5eb9ddc04fe8605\nSigned-off-by: Oliver Neukum <ONeukum@suse.com>\nCC: stable@vger.kernel.org\nSigned-off-by: Johan Hovold <johan@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/csendre/android_kernel_samsung_msm8930-common/commits/40be7029107198e5e862b90d32460dcb9282a551"},{"sha":"bdbf0bd143e18c6c355707b78cbd82636f48477c","author":{"name":"Mallikarjuna Reddy Amireddy","email":"64faf614dca1295989f342367ba1497c4cddcdee@codeaurora.org"},"message":"qseecom: Change format specifier %p to %pK\n\nFormat specifier %p can leak kernel addresses while not valuing the\nkptr_restrict system settings. When kptr_restrict is set to (1), kernel\npointers printed using the %pK format specifier will be replaced with 0's.\nSo that %pK will not leak kernel pointers to unprivileged users.\nSo change the format specifier from %p to %pK.\n\nDebugging Note : &pK prints only Zeros as address. if you need actual\naddress information, pls echo 0 to kptr_restrict.\n$ echo 0 > /proc/sys/kernel/kptr_restrict\n\nChange-Id: I0baf2be2d5a476e2e4267f20b99d0ddf5492469e\nSigned-off-by: Mallikarjuna Reddy Amireddy <mamire@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/csendre/android_kernel_samsung_msm8930-common/commits/bdbf0bd143e18c6c355707b78cbd82636f48477c"},{"sha":"76b479e618ede9a685aef5cfb39c9d6beb9dc1c0","author":{"name":"David Howells","email":"358fdf7bce8223edb2a0d846104bf62a286894d5@redhat.com"},"message":"KEYS: Disallow keyrings beginning with '.' to be joined as session keyrings\n\ncommit ee8f844e3c5a73b999edf733df1c529d6503ec2f upstream.\n\nThis fixes CVE-2016-9604.\n\nKeyrings whose name begin with a '.' are special internal keyrings and so\nuserspace isn't allowed to create keyrings by this name to prevent\nshadowing.  However, the patch that added the guard didn't fix\nKEYCTL_JOIN_SESSION_KEYRING.  Not only can that create dot-named keyrings,\nit can also subscribe to them as a session keyring if they grant SEARCH\npermission to the user.\n\nThis, for example, allows a root process to set .builtin_trusted_keys as\nits session keyring, at which point it has full access because now the\npossessor permissions are added.  This permits root to add extra public\nkeys, thereby bypassing module verification.\n\nThis also affects kexec and IMA.\n\nThis can be tested by (as root):\n\n\tkeyctl session .builtin_trusted_keys\n\tkeyctl add user a a @s\n\tkeyctl list @s\n\nwhich on my test box gives me:\n\n\t2 keys in keyring:\n\t180010936: ---lswrv     0     0 asymmetric: Build time autogenerated kernel key: ae3d4a31b82daa8e1a75b49dc2bba949fd992a05\n\t801382539: --alswrv     0     0 user: a\n\nFix this by rejecting names beginning with a '.' in the keyctl.\n\nChange-Id: I9bb919f82b62c3cf0d7dcbad9b551b8fe7d934ae\nSigned-off-by: David Howells <dhowells@redhat.com>\nAcked-by: Mimi Zohar <zohar@linux.vnet.ibm.com>\ncc: linux-ima-devel@lists.sourceforge.net\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/csendre/android_kernel_samsung_msm8930-common/commits/76b479e618ede9a685aef5cfb39c9d6beb9dc1c0"},{"sha":"1fc4c1a23aa161502ab83a0d6f7e41f70ca2492e","author":{"name":"Daniel Rosenberg","email":"ba8cfe5d21fcfdde5eed8cabcaff0549d9612a2a@google.com"},"message":"ANDROID: ion: Protect kref from userspace manipulation\n\nThis separates the kref for ion handles into two components.\nUserspace requests through the ioctl will hold at most one\nreference to the internally used kref. All additional requests\nwill increment a separate counter, and the original reference is\nonly put once that counter hits 0. This protects the kernel from\na poorly behaving userspace.\n\nBug: 34276203\n\nChange-Id: Ibc36bc4405788ed0fea7337b541cad3be2b934c0\nSigned-off-by: Daniel Rosenberg <drosen@google.com>\nGit-repo: https://android.googlesource.com/kernel/msm/\nGit-commit: 20abfcc16884a5af973a5e91dd013ddd789c44f4\n[d-cagle@codeaurora.org: Resolve style issues]\nSigned-off-by: Dennis Cagle <d-cagle@codeaurora.org>\nSigned-off-by: Arun KS <arunks@codeaurora.org>\n[arunks@codeaurora.org: ported to 3.4]","distinct":true,"url":"https://api.github.com/repos/csendre/android_kernel_samsung_msm8930-common/commits/1fc4c1a23aa161502ab83a0d6f7e41f70ca2492e"},{"sha":"11ed405282d2bee962838a2eee4b856ad0b0427d","author":{"name":"Zhen Kong","email":"b999fb1d59364862997bac94d5b793be36d63b01@codeaurora.org"},"message":"crypto: msm: check integer overflow on total data len in qcedev.c\n\nqcedev_vbuf_ablk_cipher will calculate total data length. It starts\nwith the value of \"areq->cipher_op_req.byteoffset\", which is controlled\nby the user. Make change to check if this total data length has integer\noverflow issue in qcedev_check_cipher_params.\n\nChange-Id: Ice42dca6d47eb8febfe8a34e566c69e4799fab57\nSigned-off-by: Zhen Kong <zkong@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/csendre/android_kernel_samsung_msm8930-common/commits/11ed405282d2bee962838a2eee4b856ad0b0427d"}]}
{"actor":{"display_login":"csendre"}}