{"push_id":1897820537,"size":86,"distinct_size":1,"ref":"refs/heads/linaro/linux-linaro-lsk-v4.4-android","head":"3a183de93c94237e1fd5f40d33b6ce5498c0050f","before":"1aaeb498dc16041585429644f06f449dbb12cee0","commits":[{"sha":"83863589806d00fd7b5936dcee1a897088452275","author":{"name":"Linus Torvalds","email":"ead7104581934751970e9decb2db5deb20a9e407@linux-foundation.org"},"message":"disable new gcc-7.1.1 warnings for now\n\ncommit bd664f6b3e376a8ef4990f87d08271cc2d01ba9a upstream.\n\nI made the mistake of upgrading my desktop to the new Fedora 26 that\ncomes with gcc-7.1.1.\n\nThere's nothing wrong per se that I've noticed, but I now have 1500\nlines of warnings, mostly from the new format-truncation warning\ntriggering all over the tree.\n\nWe use 'snprintf()' and friends in a lot of places, and often know that\nthe numbers are fairly small (ie a controller index or similar), but gcc\ndoesn't know that, and sees an 'int', and thinks that it could be some\nhuge number.  And then complains when our buffers are not able to fit\nthe name for the ten millionth controller.\n\nThese warnings aren't necessarily bad per se, and we probably want to\nlook through them subsystem by subsystem, but at least during the merge\nwindow they just mean that I can't even see if somebody is introducing\nany *real* problems when I pull.\n\nSo warnings disabled for now.\n\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-4.4/commits/83863589806d00fd7b5936dcee1a897088452275"},{"sha":"0ff1117c08c296aec084f9e1329f7a4ec2537ec7","author":{"name":"Arnd Bergmann","email":"72a0f6d3b182607e6d5c44b93e1abb7b23ee18f3@arndb.de"},"message":"ir-core: fix gcc-7 warning on bool arithmetic\n\ncommit bd7e31bbade02bc1e92aa00d5cf2cee2da66838a upstream.\n\ngcc-7 suggests that an expression using a bitwise not and a bitmask\non a 'bool' variable is better written using boolean logic:\n\ndrivers/media/rc/imon.c: In function 'imon_incoming_scancode':\ndrivers/media/rc/imon.c:1725:22: error: '~' on a boolean expression [-Werror=bool-operation]\n    ictx->pad_mouse = ~(ictx->pad_mouse) & 0x1;\n                      ^\ndrivers/media/rc/imon.c:1725:22: note: did you mean to use logical not?\n\nI agree.\n\nFixes: 21677cfc562a (\"V4L/DVB: ir-core: add imon driver\")\n\nSigned-off-by: Arnd Bergmann <arnd@arndb.de>\nSigned-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-4.4/commits/0ff1117c08c296aec084f9e1329f7a4ec2537ec7"},{"sha":"f440ec864fd872891895ed5fd379ff842ef76587","author":{"name":"Mauro Carvalho Chehab","email":"ea19850a825a0b2eb1de0168fb2a06f5170bd9e2@s-opensource.com"},"message":"s5p-jpeg: don't return a random width/height\n\ncommit a16e37726c444cbda91e73ed5f742e717bfe866f upstream.\n\nGcc 7.1 complains about:\n\ndrivers/media/platform/s5p-jpeg/jpeg-core.c: In function 's5p_jpeg_parse_hdr.isra.9':\ndrivers/media/platform/s5p-jpeg/jpeg-core.c:1207:12: warning: 'width' may be used uninitialized in this function [-Wmaybe-uninitialized]\n  result->w = width;\n  ~~~~~~~~~~^~~~~~~\ndrivers/media/platform/s5p-jpeg/jpeg-core.c:1208:12: warning: 'height' may be used uninitialized in this function [-Wmaybe-uninitialized]\n  result->h = height;\n  ~~~~~~~~~~^~~~~~~~\n\nIndeed the code would allow it to return a random value (although\nit shouldn't happen, in practice). So, explicitly set both to zero,\njust in case.\n\nAcked-by: Andrzej Pietrasiewicz <andrzej.p@samsung.com>\nSigned-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-4.4/commits/f440ec864fd872891895ed5fd379ff842ef76587"},{"sha":"2c1ac3721d4ab99b317ea8f9a17a6194c60b39e9","author":{"name":"Viresh Kumar","email":"4ca49bc1dcfdfc376d29da1eb07a3e0b3cd46daa@linaro.org"},"message":"thermal: cpu_cooling: Avoid accessing potentially freed structures\n\ncommit 289d72afddf83440117c35d864bf0c6309c1d011 upstream.\n\nAfter the lock is dropped, it is possible that the cpufreq_dev gets\nfreed before we call get_level() and that can cause kernel to crash.\n\nDrop the lock after we are done using the structure.\n\nFixes: 02373d7c69b4 (\"thermal: cpu_cooling: fix lockdep problems in cpu_cooling\")\nSigned-off-by: Viresh Kumar <viresh.kumar@linaro.org>\nReviewed-by: Lukasz Luba <lukasz.luba@arm.com>\nTested-by: Lukasz Luba <lukasz.luba@arm.com>\nSigned-off-by: Eduardo Valentin <edubezval@gmail.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-4.4/commits/2c1ac3721d4ab99b317ea8f9a17a6194c60b39e9"},{"sha":"a86c42f760ff19114e0a5f0ce9b64cb3927ce81d","author":{"name":"Miaoqing Pan","email":"b5eade11f2a68aa4c7c043330ed198c6df904cff@codeaurora.org"},"message":"ath9k: fix tx99 use after free\n\ncommit cf8ce1ea61b75712a154c93e40f2a5af2e4dd997 upstream.\n\nOne scenario that could lead to UAF is two threads writing\nsimultaneously to the \"tx99\" debug file. One of them would\nset the \"start\" value to true and follow to ath9k_tx99_init().\nInside the function it would set the sc->tx99_state to true\nafter allocating sc->tx99skb. Then, the other thread would\nexecute write_file_tx99() and call ath9k_tx99_deinit().\nsc->tx99_state would be freed. After that, the first thread\nwould continue inside ath9k_tx99_init() and call\nr = ath9k_tx99_send(sc, sc->tx99_skb, &txctl);\nthat would make use of the freed sc->tx99_skb memory.\n\nSigned-off-by: Miaoqing Pan <miaoqing@codeaurora.org>\nSigned-off-by: Kalle Valo <kvalo@qca.qualcomm.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-4.4/commits/a86c42f760ff19114e0a5f0ce9b64cb3927ce81d"},{"sha":"5c2828839909056379bd8c7e925026a0cef1ebdd","author":{"name":"Miaoqing Pan","email":"b5eade11f2a68aa4c7c043330ed198c6df904cff@codeaurora.org"},"message":"ath9k: fix tx99 bus error\n\ncommit bde717ab473668377fc65872398a102d40cb2d58 upstream.\n\nThe hard coded register 0x9864 and 0x9924 are invalid\nfor ar9300 chips.\n\nSigned-off-by: Miaoqing Pan <miaoqing@codeaurora.org>\nSigned-off-by: Kalle Valo <kvalo@qca.qualcomm.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-4.4/commits/5c2828839909056379bd8c7e925026a0cef1ebdd"},{"sha":"f4d41096f49efa12f50b8e4b2f72f606525029d0","author":{"name":"Johan Hovold","email":"c5aaa0c362db47011b825595d6a432662259e2f1@kernel.org"},"message":"NFC: fix broken device allocation\n\ncommit 20777bc57c346b6994f465e0d8261a7fbf213a09 upstream.\n\nCommit 7eda8b8e9677 (\"NFC: Use IDR library to assing NFC devices IDs\")\nmoved device-id allocation and struct-device initialisation from\nnfc_allocate_device() to nfc_register_device().\n\nThis broke just about every nfc-device-registration error path, which\ncontinue to call nfc_free_device() that tries to put the device\nreference of the now uninitialised (but zeroed) struct device:\n\nkobject: '(null)' (ce316420): is not initialized, yet kobject_put() is being called.\n\nThe late struct-device initialisation also meant that various work\nqueues whose names are derived from the nfc device name were also\nmisnamed:\n\n  421 root         0 SW<  [(null)_nci_cmd_]\n  422 root         0 SW<  [(null)_nci_rx_w]\n  423 root         0 SW<  [(null)_nci_tx_w]\n\nMove the id-allocation and struct-device initialisation back to\nnfc_allocate_device() and fix up the single call site which did not use\nnfc_free_device() in its error path.\n\nFixes: 7eda8b8e9677 (\"NFC: Use IDR library to assing NFC devices IDs\")\nCc: Samuel Ortiz <sameo@linux.intel.com>\nSigned-off-by: Johan Hovold <johan@kernel.org>\nSigned-off-by: Samuel Ortiz <sameo@linux.intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-4.4/commits/f4d41096f49efa12f50b8e4b2f72f606525029d0"},{"sha":"4798e468b37ba4a397c303e5ed48563d437a47bc","author":{"name":"Johan Hovold","email":"c5aaa0c362db47011b825595d6a432662259e2f1@kernel.org"},"message":"NFC: nfcmrvl_uart: add missing tty-device sanity check\n\ncommit 15e0c59f1535926a939d1df66d6edcf997d7c1b9 upstream.\n\nMake sure to check the tty-device pointer before trying to access the\nparent device to avoid dereferencing a NULL-pointer when the tty is one\nend of a Unix98 pty.\n\nFixes: e097dc624f78 (\"NFC: nfcmrvl: add UART driver\")\nCc: Vincent Cuissard <cuissard@marvell.com>\nSigned-off-by: Johan Hovold <johan@kernel.org>\nSigned-off-by: Samuel Ortiz <sameo@linux.intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-4.4/commits/4798e468b37ba4a397c303e5ed48563d437a47bc"},{"sha":"6e2b65dc2774c407de945585ca2c9e833e1f1ab2","author":{"name":"Johan Hovold","email":"c5aaa0c362db47011b825595d6a432662259e2f1@kernel.org"},"message":"NFC: nfcmrvl: do not use device-managed resources\n\ncommit 0cbe40112f42cf5e008f9127f6cd5952ba3946c7 upstream.\n\nThis specifically fixes resource leaks in the registration error paths.\n\nDevice-managed resources is a bad fit for this driver as devices can be\nregistered from the n_nci line discipline. Firstly, a tty may not even\nhave a corresponding device (should it be part of a Unix98 pty)\nsomething which would lead to a NULL-pointer dereference when\nregistering resources.\n\nSecondly, if the tty has a class device, its lifetime exceeds that of\nthe line discipline, which means that resources would leak every time\nthe line discipline is closed (or if registration fails).\n\nCurrently, the devres interface was only being used to request a reset\ngpio despite the fact that it was already explicitly freed in\nnfcmrvl_nci_unregister_dev() (along with the private data), something\nwhich also prevented the resource leak at close.\n\nNote that the driver treats gpio number 0 as invalid despite it being\nperfectly valid. This will be addressed in a follow-up patch.\n\nFixes: b2fe288eac72 (\"NFC: nfcmrvl: free reset gpio\")\nFixes: 4a2b947f56b3 (\"NFC: nfcmrvl: add chip reset management\")\nCc: Vincent Cuissard <cuissard@marvell.com>\nSigned-off-by: Johan Hovold <johan@kernel.org>\nSigned-off-by: Samuel Ortiz <sameo@linux.intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-4.4/commits/6e2b65dc2774c407de945585ca2c9e833e1f1ab2"},{"sha":"5288f3f80c4c6617d8434bf41a1d3dd19670efb6","author":{"name":"Johan Hovold","email":"c5aaa0c362db47011b825595d6a432662259e2f1@kernel.org"},"message":"NFC: nfcmrvl: use nfc-device for firmware download\n\ncommit e5834ac22948169bbd7c45996d8d4905edd20f5e upstream.\n\nUse the nfc- rather than phy-device in firmware-management code that\nneeds a valid struct device.\n\nThis specifically fixes a NULL-pointer dereference in\nnfcmrvl_fw_dnld_init() during registration when the underlying tty is\none end of a Unix98 pty.\n\nNote that the driver still uses the phy device for any debugging, which\nis fine for now.\n\nFixes: 3194c6870158 (\"NFC: nfcmrvl: add firmware download support\")\nCc: Vincent Cuissard <cuissard@marvell.com>\nSigned-off-by: Johan Hovold <johan@kernel.org>\nSigned-off-by: Samuel Ortiz <sameo@linux.intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-4.4/commits/5288f3f80c4c6617d8434bf41a1d3dd19670efb6"},{"sha":"b57a72d5aaf861774243724bdce7726c612d57bf","author":{"name":"Johan Hovold","email":"c5aaa0c362db47011b825595d6a432662259e2f1@kernel.org"},"message":"NFC: nfcmrvl: fix firmware-management initialisation\n\ncommit 45dd39b974f6632222dd5cdcbea7358a077ab0b0 upstream.\n\nThe nci-device was never deregistered in the event that\nfw-initialisation failed.\n\nFix this by moving the firmware initialisation before device\nregistration since the firmware work queue should be available before\nregistering.\n\nNote that this depends on a recent fix that moved device-name\ninitialisation back to to nci_allocate_device() as the\nfirmware-workqueue name is now derived from the nfc-device name.\n\nFixes: 3194c6870158 (\"NFC: nfcmrvl: add firmware download support\")\nCc: Vincent Cuissard <cuissard@marvell.com>\nSigned-off-by: Johan Hovold <johan@kernel.org>\nSigned-off-by: Samuel Ortiz <sameo@linux.intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-4.4/commits/b57a72d5aaf861774243724bdce7726c612d57bf"},{"sha":"ecb7abed0be9e5ced334ccd76e809cd34a00e23c","author":{"name":"Mateusz Jurczyk","email":"9dac9dbf3523a1dbbeccf3b117c6bed38acdab89@google.com"},"message":"nfc: Ensure presence of required attributes in the activate_target handler\n\ncommit a0323b979f81ad2deb2c8836eab506534891876a upstream.\n\nCheck that the NFC_ATTR_TARGET_INDEX and NFC_ATTR_PROTOCOLS attributes (in\naddition to NFC_ATTR_DEVICE_INDEX) are provided by the netlink client\nprior to accessing them. This prevents potential unhandled NULL pointer\ndereference exceptions which can be triggered by malicious user-mode\nprograms, if they omit one or both of these attributes.\n\nSigned-off-by: Mateusz Jurczyk <mjurczyk@google.com>\nAcked-by: Kees Cook <keescook@chromium.org>\nSigned-off-by: Samuel Ortiz <sameo@linux.intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-4.4/commits/ecb7abed0be9e5ced334ccd76e809cd34a00e23c"},{"sha":"f71ce1c865cb30f09fd740d730ce89098f516497","author":{"name":"Mateusz Jurczyk","email":"9dac9dbf3523a1dbbeccf3b117c6bed38acdab89@google.com"},"message":"nfc: Fix the sockaddr length sanitization in llcp_sock_connect\n\ncommit 608c4adfcabab220142ee335a2a003ccd1c0b25b upstream.\n\nFix the sockaddr length verification in the connect() handler of NFC/LLCP\nsockets, to compare against the size of the actual structure expected on\ninput (sockaddr_nfc_llcp) instead of its shorter version (sockaddr_nfc).\n\nBoth structures are defined in include/uapi/linux/nfc.h. The fields\nspecific to the _llcp extended struct are as follows:\n\n   276\t\t__u8 dsap; /* Destination SAP, if known */\n   277\t\t__u8 ssap; /* Source SAP to be bound to */\n   278\t\tchar service_name[NFC_LLCP_MAX_SERVICE_NAME]; /* Service name URI */;\n   279\t\tsize_t service_name_len;\n\nIf the caller doesn't provide a sufficiently long sockaddr buffer, these\nfields remain uninitialized (and they currently originate from the stack\nframe of the top-level sys_connect handler). They are then copied by\nllcp_sock_connect() into internal storage (nfc_llcp_sock structure), and\ncould be subsequently read back through the user-mode getsockname()\nfunction (handled by llcp_sock_getname()). This would result in the\ndisclosure of up to ~70 uninitialized bytes from the kernel stack to\nuser-mode clients capable of creating AFC_NFC sockets.\n\nSigned-off-by: Mateusz Jurczyk <mjurczyk@google.com>\nAcked-by: Kees Cook <keescook@chromium.org>\nSigned-off-by: Samuel Ortiz <sameo@linux.intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-4.4/commits/f71ce1c865cb30f09fd740d730ce89098f516497"},{"sha":"ac8f07408acd505064bd9984bece114e56d7ff91","author":{"name":"Mateusz Jurczyk","email":"9dac9dbf3523a1dbbeccf3b117c6bed38acdab89@google.com"},"message":"NFC: Add sockaddr length checks before accessing sa_family in bind handlers\n\ncommit f6a5885fc4d68e7f25ffb42b9d8d80aebb3bacbb upstream.\n\nVerify that the caller-provided sockaddr structure is large enough to\ncontain the sa_family field, before accessing it in bind() handlers of the\nAF_NFC socket. Since the syscall doesn't enforce a minimum size of the\ncorresponding memory region, very short sockaddrs (zero or one byte long)\nresult in operating on uninitialized memory while referencing .sa_family.\n\nSigned-off-by: Mateusz Jurczyk <mjurczyk@google.com>\nSigned-off-by: Samuel Ortiz <sameo@linux.intel.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-4.4/commits/ac8f07408acd505064bd9984bece114e56d7ff91"},{"sha":"5523884640e9875d8e89e057e7d5084b012e45da","author":{"name":"Adrian Hunter","email":"daa46418375a26a999430d83f18360fac0856a49@intel.com"},"message":"perf intel-pt: Move decoder error setting into one condition\n\ncommit 22c06892332d8916115525145b78e606e9cc6492 upstream.\n\nMove decoder error setting into one condition.\n\nCc'ed to stable because later fixes depend on it.\n\nSigned-off-by: Adrian Hunter <adrian.hunter@intel.com>\nCc: Andi Kleen <ak@linux.intel.com>\nLink: http://lkml.kernel.org/r/1495786658-18063-2-git-send-email-adrian.hunter@intel.com\nSigned-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-4.4/commits/5523884640e9875d8e89e057e7d5084b012e45da"},{"sha":"a4ebb58fd1241d500b53913dd35f63e697c88ed4","author":{"name":"Adrian Hunter","email":"daa46418375a26a999430d83f18360fac0856a49@intel.com"},"message":"perf intel-pt: Improve sample timestamp\n\ncommit 3f04d98e972b59706bd43d6cc75efac91f8fba50 upstream.\n\nThe decoder uses its current timestamp in samples. Usually that is a\ntimestamp that has already passed, but in some cases it is a timestamp\nfor a branch that the decoder is walking towards, and consequently\nhasn't reached. Improve that situation by using the pkt_state to\ndetermine when to use the current or previous timestamp.\n\nSigned-off-by: Adrian Hunter <adrian.hunter@intel.com>\nCc: Andi Kleen <ak@linux.intel.com>\nLink: http://lkml.kernel.org/r/1495786658-18063-3-git-send-email-adrian.hunter@intel.com\nSigned-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-4.4/commits/a4ebb58fd1241d500b53913dd35f63e697c88ed4"},{"sha":"2178b4aa56b77c23bbbd8e0b85032a31394f9d52","author":{"name":"Adrian Hunter","email":"daa46418375a26a999430d83f18360fac0856a49@intel.com"},"message":"perf intel-pt: Fix missing stack clear\n\ncommit 12b7080609097753fd8198cc1daf589be3ec1cca upstream.\n\nThe return compression stack must be cleared whenever there is a PSB. Fix\none case where that was not happening.\n\nSigned-off-by: Adrian Hunter <adrian.hunter@intel.com>\nCc: Andi Kleen <ak@linux.intel.com>\nLink: http://lkml.kernel.org/r/1495786658-18063-4-git-send-email-adrian.hunter@intel.com\nSigned-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-4.4/commits/2178b4aa56b77c23bbbd8e0b85032a31394f9d52"},{"sha":"b559fa787c625076f04feb9420dc7b1517b7328a","author":{"name":"Adrian Hunter","email":"daa46418375a26a999430d83f18360fac0856a49@intel.com"},"message":"perf intel-pt: Ensure IP is zero when state is INTEL_PT_STATE_NO_IP\n\ncommit ad7167a8cd174ba7d8c0d0ed8d8410521206d104 upstream.\n\nA value of zero is used to indicate that there is no IP. Ensure the\nvalue is zero when the state is INTEL_PT_STATE_NO_IP.\n\nSigned-off-by: Adrian Hunter <adrian.hunter@intel.com>\nCc: Andi Kleen <ak@linux.intel.com>\nLink: http://lkml.kernel.org/r/1495786658-18063-5-git-send-email-adrian.hunter@intel.com\nSigned-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-4.4/commits/b559fa787c625076f04feb9420dc7b1517b7328a"},{"sha":"3762d7ed1a43bf9f1d690e09bff3217d1a475716","author":{"name":"Adrian Hunter","email":"daa46418375a26a999430d83f18360fac0856a49@intel.com"},"message":"perf intel-pt: Clear FUP flag on error\n\ncommit 6a558f12dbe85437acbdec5e149ea07b5554eced upstream.\n\nSometimes a FUP packet is associated with a TSX transaction and a flag is\nset to indicate that. Ensure that flag is cleared on any error condition\nbecause at that point the decoder can no longer assume it is correct.\n\nSigned-off-by: Adrian Hunter <adrian.hunter@intel.com>\nCc: Andi Kleen <ak@linux.intel.com>\nLink: http://lkml.kernel.org/r/1495786658-18063-9-git-send-email-adrian.hunter@intel.com\nSigned-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-4.4/commits/3762d7ed1a43bf9f1d690e09bff3217d1a475716"},{"sha":"1e3b56033e820e0e065b3b0fc19d247118ab6532","author":{"name":"Jason A. Donenfeld","email":"99e030c4305a4e4b1828d232b8797d3ca296d80a@zx2c4.com"},"message":"Bluetooth: use constant time memory comparison for secret values\n\ncommit 329d82309824ff1082dc4a91a5bbed8c3bec1580 upstream.\n\nThis file is filled with complex cryptography. Thus, the comparisons of\nMACs and secret keys and curve points and so forth should not add timing\nattacks, which could either result in a direct forgery, or, given the\ncomplexity, some other type of attack.\n\nSigned-off-by: Jason A. Donenfeld <Jason@zx2c4.com>\nSigned-off-by: Marcel Holtmann <marcel@holtmann.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/akhilnarang/kernel_msm-4.4/commits/1e3b56033e820e0e065b3b0fc19d247118ab6532"}]}
{"actor":{"display_login":"akhilnarang"}}