{"push_id":684616587,"size":5,"distinct_size":5,"ref":"refs/heads/cm-12.1","head":"ebd859d88657d4ff19399bd6caa005c81355ca0c","before":"da3ab0612e6e939978a6d8d78bf3e50b272e07ed","commits":[{"sha":"6524efb9e4736ccb8cd19b79965eac97acf9842d","author":{"email":"86995a091f8a1385082bd10715048b52ee386a6a@google.com","name":"Lorenzo Colitti"},"message":"net: core: Support UID-based routing.\n\nThis contains the following commits:\n\n1. 0149763 net: core: Add a UID range to fib rules.\n2. 1650474 net: core: Use the socket UID in routing lookups.\n3. 0b16771 net: ipv4: Add the UID to the route cache.\n4. ee058f1 net: core: Add a RTA_UID attribute to routes.\n    This is so that userspace can do per-UID route lookups.\n\nBug: 15413527\nChange-Id: I1285474c6734614d3bda6f61d88dfe89a4af7892\nSigned-off-by: Lorenzo Colitti <lorenzo@google.com>\nGit-commit: 0b428749ce5969bc06c73855e360141b4e7126e8\nGit-repo: https://android.googlesource.com/kernel/common.git\nSigned-off-by: Ian Maund <imaund@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/aznrice/android_kernel_samsung_afyonltetmo-1/commits/6524efb9e4736ccb8cd19b79965eac97acf9842d"},{"sha":"3acc52cefc84435f3a64a605679b144bdc3cd175","author":{"email":"6ea7d46d4f923afbec11594c69f116ff20ff4572@google.com","name":"Sreeram Ramachandran"},"message":"Handle 'sk' being NULL in UID-based routing.\n\nBug: 15413527\nChange-Id: If33bebb7b52c0ebfa8dac2452607bce0c2b0faa0\nSigned-off-by: Sreeram Ramachandran <sreeram@google.com>\nGit-commit: 0836a0c191f580ed69254e0b287cdce58481e978\nGit-repo: https://android.googlesource.com/kernel/common.git\nSigned-off-by: Ian Maund <imaund@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/aznrice/android_kernel_samsung_afyonltetmo-1/commits/3acc52cefc84435f3a64a605679b144bdc3cd175"},{"sha":"1e9c09cc33bc88cc58b024e0ef4b3056aff22d8a","author":{"email":"80a2808ad150ca2adfb95dc5cdcff126251e8618@samsung.com","name":"Syam Sidhardhan"},"message":"Bluetooth: Remove unused hci_le_ltk_reply()\n\nIn this API, we were using sizeof operator for an array\ngiven as function argument, which is invalid.\nHowever this API is not used anywhere.\n\nChange-Id: I80a43472b35f0f6c117624de2b2907b37eefb786\nSigned-off-by: Syam Sidhardhan <s.syam@samsung.com>","distinct":true,"url":"https://api.github.com/repos/aznrice/android_kernel_samsung_afyonltetmo-1/commits/1e9c09cc33bc88cc58b024e0ef4b3056aff22d8a"},{"sha":"795cbbd9fda78dc6e5c57103f95db85f4d379984","author":{"email":"d6e1285e1c84d3d5885c2124fdacc780e9fc0a94@tycho.nsa.gov","name":"Stephen Smalley"},"message":"Enable setting security contexts on rootfs inodes.\n\nrootfs (ramfs) can support setting of security contexts\nby userspace due to the vfs fallback behavior of calling\nthe security module to set the in-core inode state\nfor security.* attributes when the filesystem does not\nprovide an xattr handler.  No xattr handler required\nas the inodes are pinned in memory and have no backing\nstore.\n\nThis is useful in allowing early userspace to label individual\nfiles within a rootfs while still providing a policy-defined\ndefault via genfs.\n\nSigned-off-by: Stephen Smalley <sds@tycho.nsa.gov>","distinct":true,"url":"https://api.github.com/repos/aznrice/android_kernel_samsung_afyonltetmo-1/commits/795cbbd9fda78dc6e5c57103f95db85f4d379984"},{"sha":"ebd859d88657d4ff19399bd6caa005c81355ca0c","author":{"email":"e642b69ed2fc111e09ffdc37feb733a52253340d@oracle.com","name":"Sasha Levin"},"message":"KEYS: close race between key lookup and freeing\n\nWhen a key is being garbage collected, it's key->user would get put before\nthe ->destroy() callback is called, where the key is removed from it's\nrespective tracking structures.\n\nThis leaves a key hanging in a semi-invalid state which leaves a window open\nfor a different task to try an access key->user. An example is\nfind_keyring_by_name() which would dereference key->user for a key that is\nin the process of being garbage collected (where key->user was freed but\n->destroy() wasn't called yet - so it's still present in the linked list).\n\nThis would cause either a panic, or corrupt memory.\n\nChange-Id: Ic74246dc2dcc593f04f71063e3301e7356d588b7\nSigned-off-by: Sasha Levin <sasha.levin@oracle.com>","distinct":true,"url":"https://api.github.com/repos/aznrice/android_kernel_samsung_afyonltetmo-1/commits/ebd859d88657d4ff19399bd6caa005c81355ca0c"}]}