{"push_id":4243532896,"size":49,"distinct_size":49,"ref":"refs/heads/panda-rebase","head":"52ebdd2537ecc970f559d048339ab63ae03d2028","before":"b909c84b1ef2eff9eea74250fd0607bfa98a5f82","commits":[{"sha":"eda053db0782296e4c074e9e3096630581bccdae","author":{"name":"Mikulas Patocka","email":"52f8f9962b7f38d8269c63c0859d68147c8d10f0@redhat.com"},"message":"dm snapshot: use mutex instead of rw_semaphore\n\n[ Upstream commit ae1093be5a0ef997833e200a0dafb9ed0b1ff4fe ]\n\nThe rw_semaphore is acquired for read only in two places, neither is\nperformance-critical.  So replace it with a mutex -- which is more\nefficient.\n\nSigned-off-by: Mikulas Patocka <mpatocka@redhat.com>\nSigned-off-by: Mike Snitzer <snitzer@redhat.com>\nSigned-off-by: Sasha Levin <sashal@kernel.org>","distinct":true,"url":"https://api.github.com/repos/Pzqqt/android_kernel_xiaomi_whyred/commits/eda053db0782296e4c074e9e3096630581bccdae"},{"sha":"e10ef97a2ec45b1323939f978055b08429d4b4c1","author":{"name":"Mikulas Patocka","email":"52f8f9962b7f38d8269c63c0859d68147c8d10f0@redhat.com"},"message":"dm snapshot: introduce account_start_copy() and account_end_copy()\n\n[ Upstream commit a2f83e8b0c82c9500421a26c49eb198b25fcdea3 ]\n\nThis simple refactoring moves code for modifying the semaphore cow_count\ninto separate functions to prepare for changes that will extend these\nmethods to provide for a more sophisticated mechanism for COW\nthrottling.\n\nSigned-off-by: Mikulas Patocka <mpatocka@redhat.com>\nReviewed-by: Nikos Tsironis <ntsironis@arrikto.com>\nSigned-off-by: Mike Snitzer <snitzer@redhat.com>\nSigned-off-by: Sasha Levin <sashal@kernel.org>","distinct":true,"url":"https://api.github.com/repos/Pzqqt/android_kernel_xiaomi_whyred/commits/e10ef97a2ec45b1323939f978055b08429d4b4c1"},{"sha":"40dbcbebf0e0b51eeef8ae150a62ffd03ee57c57","author":{"name":"Mikulas Patocka","email":"52f8f9962b7f38d8269c63c0859d68147c8d10f0@redhat.com"},"message":"dm snapshot: rework COW throttling to fix deadlock\n\n[ Upstream commit b21555786f18cd77f2311ad89074533109ae3ffa ]\n\nCommit 721b1d98fb517a (\"dm snapshot: Fix excessive memory usage and\nworkqueue stalls\") introduced a semaphore to limit the maximum number of\nin-flight kcopyd (COW) jobs.\n\nThe implementation of this throttling mechanism is prone to a deadlock:\n\n1. One or more threads write to the origin device causing COW, which is\n   performed by kcopyd.\n\n2. At some point some of these threads might reach the s->cow_count\n   semaphore limit and block in down(&s->cow_count), holding a read lock\n   on _origins_lock.\n\n3. Someone tries to acquire a write lock on _origins_lock, e.g.,\n   snapshot_ctr(), which blocks because the threads at step (2) already\n   hold a read lock on it.\n\n4. A COW operation completes and kcopyd runs dm-snapshot's completion\n   callback, which ends up calling pending_complete().\n   pending_complete() tries to resubmit any deferred origin bios. This\n   requires acquiring a read lock on _origins_lock, which blocks.\n\n   This happens because the read-write semaphore implementation gives\n   priority to writers, meaning that as soon as a writer tries to enter\n   the critical section, no readers will be allowed in, until all\n   writers have completed their work.\n\n   So, pending_complete() waits for the writer at step (3) to acquire\n   and release the lock. This writer waits for the readers at step (2)\n   to release the read lock and those readers wait for\n   pending_complete() (the kcopyd thread) to signal the s->cow_count\n   semaphore: DEADLOCK.\n\nThe above was thoroughly analyzed and documented by Nikos Tsironis as\npart of his initial proposal for fixing this deadlock, see:\nhttps://www.redhat.com/archives/dm-devel/2019-October/msg00001.html\n\nFix this deadlock by reworking COW throttling so that it waits without\nholding any locks. Add a variable 'in_progress' that counts how many\nkcopyd jobs are running. A function wait_for_in_progress() will sleep if\n'in_progress' is over the limit. It drops _origins_lock in order to\navoid the deadlock.\n\nReported-by: Guruswamy Basavaiah <guru2018@gmail.com>\nReported-by: Nikos Tsironis <ntsironis@arrikto.com>\nReviewed-by: Nikos Tsironis <ntsironis@arrikto.com>\nTested-by: Nikos Tsironis <ntsironis@arrikto.com>\nFixes: 721b1d98fb51 (\"dm snapshot: Fix excessive memory usage and workqueue stalls\")\nCc: stable@vger.kernel.org # v5.0+\nDepends-on: 4a3f111a73a8c (\"dm snapshot: introduce account_start_copy() and account_end_copy()\")\nSigned-off-by: Mikulas Patocka <mpatocka@redhat.com>\nSigned-off-by: Mike Snitzer <snitzer@redhat.com>\nSigned-off-by: Sasha Levin <sashal@kernel.org>","distinct":true,"url":"https://api.github.com/repos/Pzqqt/android_kernel_xiaomi_whyred/commits/40dbcbebf0e0b51eeef8ae150a62ffd03ee57c57"},{"sha":"d9b19e637bd9a1fbf318416e040073233969e582","author":{"name":"Kent Overstreet","email":"b05121bc1076dfe178a210973695cebd90cde508@gmail.com"},"message":"dm: Use kzalloc for all structs with embedded biosets/mempools\n\n[ Upstream commit d377535405686f735b90a8ad4ba269484cd7c96e ]\n\nmempool_init()/bioset_init() require that the mempools/biosets be zeroed\nfirst; they probably should not _require_ this, but not allocating those\nstructs with kzalloc is a fairly nonsensical thing to do (calling\nmempool_exit()/bioset_exit() on an uninitialized mempool/bioset is legal\nand safe, but only works if said memory was zeroed.)\n\nAcked-by: Mike Snitzer <snitzer@redhat.com>\nSigned-off-by: Kent Overstreet <kent.overstreet@gmail.com>\nSigned-off-by: Jens Axboe <axboe@kernel.dk>\nSigned-off-by: Sasha Levin <sashal@kernel.org>","distinct":true,"url":"https://api.github.com/repos/Pzqqt/android_kernel_xiaomi_whyred/commits/d9b19e637bd9a1fbf318416e040073233969e582"},{"sha":"548967e6351374b363d78f20d9bbe621c5e9003e","author":{"name":"Phil Elwell","email":"e888d2bd6f13f82caa51a37c03d034c76f661ba3@raspberrypi.org"},"message":"sc16is7xx: Fix for \"Unexpected interrupt: 8\"\n\n[ Upstream commit 30ec514d440cf2c472c8e4b0079af2c731f71a3e ]\n\nThe SC16IS752 has an Enhanced Feature Register which is aliased at the\nsame address as the Interrupt Identification Register; accessing it\nrequires that a magic value is written to the Line Configuration\nRegister. If an interrupt is raised while the EFR is mapped in then\nthe ISR won't be able to access the IIR, leading to the \"Unexpected\ninterrupt\" error messages.\n\nAvoid the problem by claiming a mutex around accesses to the EFR\nregister, also claiming the mutex in the interrupt handler work\nitem (this is equivalent to disabling interrupts to interlock against\na non-threaded interrupt handler).\n\nSee: https://github.com/raspberrypi/linux/issues/2529\n\nSigned-off-by: Phil Elwell <phil@raspberrypi.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Sasha Levin <sashal@kernel.org>","distinct":true,"url":"https://api.github.com/repos/Pzqqt/android_kernel_xiaomi_whyred/commits/548967e6351374b363d78f20d9bbe621c5e9003e"},{"sha":"78c5c5e077aedfa75df02a5c97a14e44b1e8083c","author":{"name":"Kan Liang","email":"6e4ed0645dbf05e706dc43d69b381839dca8944b@linux.intel.com"},"message":"x86/cpu: Add Atom Tremont (Jacobsville)\n\n[ Upstream commit 00ae831dfe4474ef6029558f5eb3ef0332d80043 ]\n\nAdd the Atom Tremont model number to the Intel family list.\n\n[ Tony: Also update comment at head of file to say \"_X\" suffix is\n  also used for microserver parts. ]\n\nSigned-off-by: Kan Liang <kan.liang@linux.intel.com>\nSigned-off-by: Qiuxu Zhuo <qiuxu.zhuo@intel.com>\nSigned-off-by: Tony Luck <tony.luck@intel.com>\nSigned-off-by: Borislav Petkov <bp@suse.de>\nCc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>\nCc: Aristeu Rozanski <aris@redhat.com>\nCc: \"H. Peter Anvin\" <hpa@zytor.com>\nCc: Ingo Molnar <mingo@redhat.com>\nCc: linux-edac <linux-edac@vger.kernel.org>\nCc: Mauro Carvalho Chehab <mchehab@s-opensource.com>\nCc: Megha Dey <megha.dey@linux.intel.com>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Qiuxu Zhuo <qiuxu.zhuo@intel.com>\nCc: Rajneesh Bhardwaj <rajneesh.bhardwaj@intel.com>\nCc: Thomas Gleixner <tglx@linutronix.de>\nCc: x86-ml <x86@kernel.org>\nLink: https://lkml.kernel.org/r/20190125195902.17109-4-tony.luck@intel.com\nSigned-off-by: Sasha Levin <sashal@kernel.org>","distinct":true,"url":"https://api.github.com/repos/Pzqqt/android_kernel_xiaomi_whyred/commits/78c5c5e077aedfa75df02a5c97a14e44b1e8083c"},{"sha":"b3ffb896a35600f2f67559ad61bc97faaca84b21","author":{"name":"Brian Norris","email":"67059238af8e1945c40edb274ce1d51ba595dbf3@chromium.org"},"message":"scripts/setlocalversion: Improve -dirty check with git-status --no-optional-locks\n\n[ Upstream commit ff64dd4857303dd5550faed9fd598ac90f0f2238 ]\n\ngit-diff-index does not refresh the index for you, so using it for a\n\"-dirty\" check can give misleading results. Commit 6147b1cf19651\n(\"scripts/setlocalversion: git: Make -dirty check more robust\") tried to\nfix this by switching to git-status, but it overlooked the fact that\ngit-status also writes to the .git directory of the source tree, which\nis definitely not kosher for an out-of-tree (O=) build. That is getting\nreverted.\n\nFortunately, git-status now supports avoiding writing to the index via\nthe --no-optional-locks flag, as of git 2.14. It still calculates an\nup-to-date index, but it avoids writing it out to the .git directory.\n\nSo, let's retry the solution from commit 6147b1cf19651 using this new\nflag first, and if it fails, we assume this is an older version of git\nand just use the old git-diff-index method.\n\nIt's hairy to get the 'grep -vq' (inverted matching) correct by stashing\nthe output of git-status (you have to be careful about the difference\nbetwen \"empty stdin\" and \"blank line on stdin\"), so just pipe the output\ndirectly to grep and use a regex that's good enough for both the\ngit-status and git-diff-index version.\n\nCc: Christian Kujau <lists@nerdbynature.de>\nCc: Guenter Roeck <linux@roeck-us.net>\nSuggested-by: Alexander Kapshuk <alexander.kapshuk@gmail.com>\nSigned-off-by: Brian Norris <briannorris@chromium.org>\nTested-by: Genki Sky <sky@genki.is>\nSigned-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>\nSigned-off-by: Sasha Levin <sashal@kernel.org>","distinct":true,"url":"https://api.github.com/repos/Pzqqt/android_kernel_xiaomi_whyred/commits/b3ffb896a35600f2f67559ad61bc97faaca84b21"},{"sha":"fcc987e8792aba817060133a1ab867574749bacb","author":{"name":"Jan-Marek Glogowski","email":"9cd2e21a36999b6e7c386c0227f01ea23e293853@fbihome.de"},"message":"usb: handle warm-reset port requests on hub resume\n\n[ Upstream commit 4fdc1790e6a9ef22399c6bc6e63b80f4609f3b7e ]\n\nOn plug-in of my USB-C device, its USB_SS_PORT_LS_SS_INACTIVE\nlink state bit is set. Greping all the kernel for this bit shows\nthat the port status requests a warm-reset this way.\n\nThis just happens, if its the only device on the root hub, the hub\ntherefore resumes and the HCDs status_urb isn't yet available.\nIf a warm-reset request is detected, this sets the hubs event_bits,\nwhich will prevent any auto-suspend and allows the hubs workqueue\nto warm-reset the port later in port_event.\n\nSigned-off-by: Jan-Marek Glogowski <glogow@fbihome.de>\nAcked-by: Alan Stern <stern@rowland.harvard.edu>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Sasha Levin <sashal@kernel.org>","distinct":true,"url":"https://api.github.com/repos/Pzqqt/android_kernel_xiaomi_whyred/commits/fcc987e8792aba817060133a1ab867574749bacb"},{"sha":"3d11387f82bf19b2e200fdd2cb69cc88607b07f8","author":{"name":"Kees Cook","email":"50cb10d2be062154b17ab4d66a4eab34f1cf1c84@chromium.org"},"message":"exec: load_script: Do not exec truncated interpreter path\n\n[ Upstream commit b5372fe5dc84235dbe04998efdede3c4daa866a9 ]\n\nCommit 8099b047ecc4 (\"exec: load_script: don't blindly truncate\nshebang string\") was trying to protect against a confused exec of a\ntruncated interpreter path. However, it was overeager and also refused\nto truncate arguments as well, which broke userspace, and it was\nreverted. This attempts the protection again, but allows arguments to\nremain truncated. In an effort to improve readability, helper functions\nand comments have been added.\n\nCo-developed-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Kees Cook <keescook@chromium.org>\nCc: Andrew Morton <akpm@linux-foundation.org>\nCc: Oleg Nesterov <oleg@redhat.com>\nCc: Samuel Dionne-Riel <samuel@dionne-riel.com>\nCc: Richard Weinberger <richard.weinberger@gmail.com>\nCc: Graham Christensen <graham@grahamc.com>\nCc: Michal Hocko <mhocko@suse.com>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Sasha Levin <sashal@kernel.org>","distinct":true,"url":"https://api.github.com/repos/Pzqqt/android_kernel_xiaomi_whyred/commits/3d11387f82bf19b2e200fdd2cb69cc88607b07f8"},{"sha":"74ebfbc9ec0c8f94e9de75bdee36b0e1b87a6a71","author":{"name":"Pascal Bouwmann","email":"99cd0f1c343e93e9fb235f8bdfe26c9a29da9663@tau-tec.de"},"message":"iio: fix center temperature of bmc150-accel-core\n\n[ Upstream commit 6c59a962e081df6d8fe43325bbfabec57e0d4751 ]\n\nThe center temperature of the supported devices stored in the constant\nBMC150_ACCEL_TEMP_CENTER_VAL is not 24 degrees but 23 degrees.\n\nIt seems that some datasheets were inconsistent on this value leading\nto the error.  For most usecases will only make minor difference so\nnot queued for stable.\n\nSigned-off-by: Pascal Bouwmann <bouwmann@tau-tec.de>\nSigned-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>\nSigned-off-by: Sasha Levin <sashal@kernel.org>","distinct":true,"url":"https://api.github.com/repos/Pzqqt/android_kernel_xiaomi_whyred/commits/74ebfbc9ec0c8f94e9de75bdee36b0e1b87a6a71"},{"sha":"bd7d309e52f959df89022cc5414ea0108f57c13e","author":{"name":"Steve MacLean","email":"268ad175a9a22309a2d803c5722864d98258bb78@microsoft.com"},"message":"perf map: Fix overlapped map handling\n\n[ Upstream commit ee212d6ea20887c0ef352be8563ca13dbf965906 ]\n\nWhenever an mmap/mmap2 event occurs, the map tree must be updated to add a new\nentry. If a new map overlaps a previous map, the overlapped section of the\nprevious map is effectively unmapped, but the non-overlapping sections are\nstill valid.\n\nmaps__fixup_overlappings() is responsible for creating any new map entries from\nthe previously overlapped map. It optionally creates a before and an after map.\n\nWhen creating the after map the existing code failed to adjust the map.pgoff.\nThis meant the new after map would incorrectly calculate the file offset\nfor the ip. This results in incorrect symbol name resolution for any ip in the\nafter region.\n\nMake maps__fixup_overlappings() correctly populate map.pgoff.\n\nAdd an assert that new mapping matches old mapping at the beginning of\nthe after map.\n\nCommitter-testing:\n\nValidated correct parsing of libcoreclr.so symbols from .NET Core 3.0 preview9\n(which didn't strip symbols).\n\nPreparation:\n\n  ~/dotnet3.0-preview9/dotnet new webapi -o perfSymbol\n  cd perfSymbol\n  ~/dotnet3.0-preview9/dotnet publish\n  perf record ~/dotnet3.0-preview9/dotnet \\\n      bin/Debug/netcoreapp3.0/publish/perfSymbol.dll\n  ^C\n\nBefore:\n\n  perf script --show-mmap-events 2>&1 | grep -e MMAP -e unknown |\\\n     grep libcoreclr.so | head -n 4\n        dotnet  1907 373352.698780: PERF_RECORD_MMAP2 1907/1907: \\\n            [0x7fe615726000(0x768000) @ 0 08:02 5510620 765057155]: \\\n            r-xp .../3.0.0-preview9-19423-09/libcoreclr.so\n        dotnet  1907 373352.701091: PERF_RECORD_MMAP2 1907/1907: \\\n            [0x7fe615974000(0x1000) @ 0x24e000 08:02 5510620 765057155]: \\\n            rwxp .../3.0.0-preview9-19423-09/libcoreclr.so\n        dotnet  1907 373352.701241: PERF_RECORD_MMAP2 1907/1907: \\\n            [0x7fe615c42000(0x1000) @ 0x51c000 08:02 5510620 765057155]: \\\n            rwxp .../3.0.0-preview9-19423-09/libcoreclr.so\n        dotnet  1907 373352.705249:     250000 cpu-clock: \\\n             7fe6159a1f99 [unknown] \\\n             (.../3.0.0-preview9-19423-09/libcoreclr.so)\n\nAfter:\n\n  perf script --show-mmap-events 2>&1 | grep -e MMAP -e unknown |\\\n     grep libcoreclr.so | head -n 4\n        dotnet  1907 373352.698780: PERF_RECORD_MMAP2 1907/1907: \\\n            [0x7fe615726000(0x768000) @ 0 08:02 5510620 765057155]: \\\n            r-xp .../3.0.0-preview9-19423-09/libcoreclr.so\n        dotnet  1907 373352.701091: PERF_RECORD_MMAP2 1907/1907: \\\n            [0x7fe615974000(0x1000) @ 0x24e000 08:02 5510620 765057155]: \\\n            rwxp .../3.0.0-preview9-19423-09/libcoreclr.so\n        dotnet  1907 373352.701241: PERF_RECORD_MMAP2 1907/1907: \\\n            [0x7fe615c42000(0x1000) @ 0x51c000 08:02 5510620 765057155]: \\\n            rwxp .../3.0.0-preview9-19423-09/libcoreclr.so\n\nAll the [unknown] symbols were resolved.\n\nSigned-off-by: Steve MacLean <Steve.MacLean@Microsoft.com>\nTested-by: Brian Robbins <brianrob@microsoft.com>\nAcked-by: Jiri Olsa <jolsa@kernel.org>\nCc: Alexander Shishkin <alexander.shishkin@linux.intel.com>\nCc: Andi Kleen <ak@linux.intel.com>\nCc: Davidlohr Bueso <dave@stgolabs.net>\nCc: Eric Saint-Etienne <eric.saint.etienne@oracle.com>\nCc: John Keeping <john@metanate.com>\nCc: John Salem <josalem@microsoft.com>\nCc: Leo Yan <leo.yan@linaro.org>\nCc: Mark Rutland <mark.rutland@arm.com>\nCc: Namhyung Kim <namhyung@kernel.org>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Song Liu <songliubraving@fb.com>\nCc: Stephane Eranian <eranian@google.com>\nCc: Tom McDonald <thomas.mcdonald@microsoft.com>\nLink: http://lore.kernel.org/lkml/BN8PR21MB136270949F22A6A02335C238F7800@BN8PR21MB1362.namprd21.prod.outlook.com\nSigned-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>\nSigned-off-by: Sasha Levin <sashal@kernel.org>","distinct":true,"url":"https://api.github.com/repos/Pzqqt/android_kernel_xiaomi_whyred/commits/bd7d309e52f959df89022cc5414ea0108f57c13e"},{"sha":"f8ae287cff0733a064a331ad9a9756d163520711","author":{"name":"Bart Van Assche","email":"89ed62d80e76c0eb24ee0d6433b48a91c2273b5e@acm.org"},"message":"RDMA/iwcm: Fix a lock inversion issue\n\n[ Upstream commit b66f31efbdad95ec274345721d99d1d835e6de01 ]\n\nThis patch fixes the lock inversion complaint:\n\n============================================\nWARNING: possible recursive locking detected\n5.3.0-rc7-dbg+ #1 Not tainted\n--------------------------------------------\nkworker/u16:6/171 is trying to acquire lock:\n00000000035c6e6c (&id_priv->handler_mutex){+.+.}, at: rdma_destroy_id+0x78/0x4a0 [rdma_cm]\n\nbut task is already holding lock:\n00000000bc7c307d (&id_priv->handler_mutex){+.+.}, at: iw_conn_req_handler+0x151/0x680 [rdma_cm]\n\nother info that might help us debug this:\n Possible unsafe locking scenario:\n\n       CPU0\n       ----\n  lock(&id_priv->handler_mutex);\n  lock(&id_priv->handler_mutex);\n\n *** DEADLOCK ***\n\n May be due to missing lock nesting notation\n\n3 locks held by kworker/u16:6/171:\n #0: 00000000e2eaa773 ((wq_completion)iw_cm_wq){+.+.}, at: process_one_work+0x472/0xac0\n #1: 000000001efd357b ((work_completion)(&work->work)#3){+.+.}, at: process_one_work+0x476/0xac0\n #2: 00000000bc7c307d (&id_priv->handler_mutex){+.+.}, at: iw_conn_req_handler+0x151/0x680 [rdma_cm]\n\nstack backtrace:\nCPU: 3 PID: 171 Comm: kworker/u16:6 Not tainted 5.3.0-rc7-dbg+ #1\nHardware name: Bochs Bochs, BIOS Bochs 01/01/2011\nWorkqueue: iw_cm_wq cm_work_handler [iw_cm]\nCall Trace:\n dump_stack+0x8a/0xd6\n __lock_acquire.cold+0xe1/0x24d\n lock_acquire+0x106/0x240\n __mutex_lock+0x12e/0xcb0\n mutex_lock_nested+0x1f/0x30\n rdma_destroy_id+0x78/0x4a0 [rdma_cm]\n iw_conn_req_handler+0x5c9/0x680 [rdma_cm]\n cm_work_handler+0xe62/0x1100 [iw_cm]\n process_one_work+0x56d/0xac0\n worker_thread+0x7a/0x5d0\n kthread+0x1bc/0x210\n ret_from_fork+0x24/0x30\n\nThis is not a bug as there are actually two lock classes here.\n\nLink: https://lore.kernel.org/r/20190930231707.48259-3-bvanassche@acm.org\nFixes: de910bd92137 (\"RDMA/cma: Simplify locking needed for serialization of callbacks\")\nSigned-off-by: Bart Van Assche <bvanassche@acm.org>\nReviewed-by: Jason Gunthorpe <jgg@mellanox.com>\nSigned-off-by: Jason Gunthorpe <jgg@mellanox.com>\nSigned-off-by: Sasha Levin <sashal@kernel.org>","distinct":true,"url":"https://api.github.com/repos/Pzqqt/android_kernel_xiaomi_whyred/commits/f8ae287cff0733a064a331ad9a9756d163520711"},{"sha":"2a2437482cc00b48b66c7b8b93a1b2aae86b2206","author":{"name":"Austin Kim","email":"368a083f77a70afae283446f997dc5738af61439@gmail.com"},"message":"fs: cifs: mute -Wunused-const-variable message\n\n[ Upstream commit dd19c106a36690b47bb1acc68372f2b472b495b8 ]\n\nAfter 'Initial git repository build' commit,\n'mapping_table_ERRHRD' variable has not been used.\n\nSo 'mapping_table_ERRHRD' const variable could be removed\nto mute below warning message:\n\n   fs/cifs/netmisc.c:120:40: warning: unused variable 'mapping_table_ERRHRD' [-Wunused-const-variable]\n   static const struct smb_to_posix_error mapping_table_ERRHRD[] = {\n                                           ^\nSigned-off-by: Austin Kim <austindh.kim@gmail.com>\nSigned-off-by: Steve French <stfrench@microsoft.com>\nSigned-off-by: Sasha Levin <sashal@kernel.org>","distinct":true,"url":"https://api.github.com/repos/Pzqqt/android_kernel_xiaomi_whyred/commits/2a2437482cc00b48b66c7b8b93a1b2aae86b2206"},{"sha":"5290a8f6585b310cb55e393b4f6674f2347de408","author":{"name":"Adam Ford","email":"b78e2d58470ceb4ca2120c00df307b89e7576873@gmail.com"},"message":"serial: mctrl_gpio: Check for NULL pointer\n\n[ Upstream commit 37e3ab00e4734acc15d96b2926aab55c894f4d9c ]\n\nWhen using mctrl_gpio_to_gpiod, it dereferences gpios into a single\nrequested GPIO.  This dereferencing can break if gpios is NULL,\nso this patch adds a NULL check before dereferencing it.  If\ngpios is NULL, this function will also return NULL.\n\nSigned-off-by: Adam Ford <aford173@gmail.com>\nReviewed-by: Yegor Yefremov <yegorslists@googlemail.com>\nLink: https://lore.kernel.org/r/20191006163314.23191-1-aford173@gmail.com\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Sasha Levin <sashal@kernel.org>","distinct":true,"url":"https://api.github.com/repos/Pzqqt/android_kernel_xiaomi_whyred/commits/5290a8f6585b310cb55e393b4f6674f2347de408"},{"sha":"492fbc76b94e55fb4d2fa40a756e4c20218f9b32","author":{"name":"Lukas Wunner","email":"65adda4326914576405c9e3a62f4904d96573863@wunner.de"},"message":"efi/cper: Fix endianness of PCIe class code\n\n[ Upstream commit 6fb9367a15d1a126d222d738b2702c7958594a5f ]\n\nThe CPER parser assumes that the class code is big endian, but at least\non this edk2-derived Intel Purley platform it's little endian:\n\n    efi: EFI v2.50 by EDK II BIOS ID:PLYDCRB1.86B.0119.R05.1701181843\n    DMI: Intel Corporation PURLEY/PURLEY, BIOS PLYDCRB1.86B.0119.R05.1701181843 01/18/2017\n\n    {1}[Hardware Error]:   device_id: 0000:5d:00.0\n    {1}[Hardware Error]:   slot: 0\n    {1}[Hardware Error]:   secondary_bus: 0x5e\n    {1}[Hardware Error]:   vendor_id: 0x8086, device_id: 0x2030\n    {1}[Hardware Error]:   class_code: 000406\n                                       ^^^^^^ (should be 060400)\n\nSigned-off-by: Lukas Wunner <lukas@wunner.de>\nSigned-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>\nCc: Ben Dooks <ben.dooks@codethink.co.uk>\nCc: Dave Young <dyoung@redhat.com>\nCc: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>\nCc: Jerry Snitselaar <jsnitsel@redhat.com>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Lyude Paul <lyude@redhat.com>\nCc: Matthew Garrett <mjg59@google.com>\nCc: Octavian Purdila <octavian.purdila@intel.com>\nCc: Peter Jones <pjones@redhat.com>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Scott Talbert <swt@techie.net>\nCc: Thomas Gleixner <tglx@linutronix.de>\nCc: linux-efi@vger.kernel.org\nCc: linux-integrity@vger.kernel.org\nLink: https://lkml.kernel.org/r/20191002165904.8819-2-ard.biesheuvel@linaro.org\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\nSigned-off-by: Sasha Levin <sashal@kernel.org>","distinct":true,"url":"https://api.github.com/repos/Pzqqt/android_kernel_xiaomi_whyred/commits/492fbc76b94e55fb4d2fa40a756e4c20218f9b32"},{"sha":"20cd8a5d2224f9d56ff4f3a19746dce5f92920a4","author":{"name":"Dave Young","email":"5716cc40769303914dac486db0fc6ac4cba9419e@redhat.com"},"message":"efi/x86: Do not clean dummy variable in kexec path\n\n[ Upstream commit 2ecb7402cfc7f22764e7bbc80790e66eadb20560 ]\n\nkexec reboot fails randomly in UEFI based KVM guest.  The firmware\njust resets while calling efi_delete_dummy_variable();  Unfortunately\nI don't know how to debug the firmware, it is also possible a potential\nproblem on real hardware as well although nobody reproduced it.\n\nThe intention of the efi_delete_dummy_variable is to trigger garbage collection\nwhen entering virtual mode.  But SetVirtualAddressMap can only run once\nfor each physical reboot, thus kexec_enter_virtual_mode() is not necessarily\na good place to clean a dummy object.\n\nDrop the efi_delete_dummy_variable so that kexec reboot can work.\n\nSigned-off-by: Dave Young <dyoung@redhat.com>\nSigned-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>\nAcked-by: Matthew Garrett <mjg59@google.com>\nCc: Ben Dooks <ben.dooks@codethink.co.uk>\nCc: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>\nCc: Jerry Snitselaar <jsnitsel@redhat.com>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Lukas Wunner <lukas@wunner.de>\nCc: Lyude Paul <lyude@redhat.com>\nCc: Octavian Purdila <octavian.purdila@intel.com>\nCc: Peter Jones <pjones@redhat.com>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Scott Talbert <swt@techie.net>\nCc: Thomas Gleixner <tglx@linutronix.de>\nCc: linux-efi@vger.kernel.org\nCc: linux-integrity@vger.kernel.org\nLink: https://lkml.kernel.org/r/20191002165904.8819-8-ard.biesheuvel@linaro.org\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\nSigned-off-by: Sasha Levin <sashal@kernel.org>","distinct":true,"url":"https://api.github.com/repos/Pzqqt/android_kernel_xiaomi_whyred/commits/20cd8a5d2224f9d56ff4f3a19746dce5f92920a4"},{"sha":"3cbc762f5c763035c5978e449318670325673f3b","author":{"name":"Jia-Ju Bai","email":"4f6d392e422d1b8f381e5a7c1b9b3c46d9851e8b@gmail.com"},"message":"fs: ocfs2: fix possible null-pointer dereferences in ocfs2_xa_prepare_entry()\n\n[ Upstream commit 56e94ea132bb5c2c1d0b60a6aeb34dcb7d71a53d ]\n\nIn ocfs2_xa_prepare_entry(), there is an if statement on line 2136 to\ncheck whether loc->xl_entry is NULL:\n\n    if (loc->xl_entry)\n\nWhen loc->xl_entry is NULL, it is used on line 2158:\n\n    ocfs2_xa_add_entry(loc, name_hash);\n        loc->xl_entry->xe_name_hash = cpu_to_le32(name_hash);\n        loc->xl_entry->xe_name_offset = cpu_to_le16(loc->xl_size);\n\nand line 2164:\n\n    ocfs2_xa_add_namevalue(loc, xi);\n        loc->xl_entry->xe_value_size = cpu_to_le64(xi->xi_value_len);\n        loc->xl_entry->xe_name_len = xi->xi_name_len;\n\nThus, possible null-pointer dereferences may occur.\n\nTo fix these bugs, if loc-xl_entry is NULL, ocfs2_xa_prepare_entry()\nabnormally returns with -EINVAL.\n\nThese bugs are found by a static analysis tool STCheck written by us.\n\n[akpm@linux-foundation.org: remove now-unused ocfs2_xa_add_entry()]\nLink: http://lkml.kernel.org/r/20190726101447.9153-1-baijiaju1990@gmail.com\nSigned-off-by: Jia-Ju Bai <baijiaju1990@gmail.com>\nReviewed-by: Joseph Qi <joseph.qi@linux.alibaba.com>\nCc: Mark Fasheh <mark@fasheh.com>\nCc: Joel Becker <jlbec@evilplan.org>\nCc: Junxiao Bi <junxiao.bi@oracle.com>\nCc: Changwei Ge <gechangwei@live.cn>\nCc: Gang He <ghe@suse.com>\nCc: Jun Piao <piaojun@huawei.com>\nCc: Stephen Rothwell <sfr@canb.auug.org.au>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Sasha Levin <sashal@kernel.org>","distinct":true,"url":"https://api.github.com/repos/Pzqqt/android_kernel_xiaomi_whyred/commits/3cbc762f5c763035c5978e449318670325673f3b"},{"sha":"23d94f1fec0aec5e547ae0c96c5da28d12fa652c","author":{"name":"Jia-Ju Bai","email":"4f6d392e422d1b8f381e5a7c1b9b3c46d9851e8b@gmail.com"},"message":"fs: ocfs2: fix a possible null-pointer dereference in ocfs2_info_scan_inode_alloc()\n\n[ Upstream commit 2abb7d3b12d007c30193f48bebed781009bebdd2 ]\n\nIn ocfs2_info_scan_inode_alloc(), there is an if statement on line 283\nto check whether inode_alloc is NULL:\n\n    if (inode_alloc)\n\nWhen inode_alloc is NULL, it is used on line 287:\n\n    ocfs2_inode_lock(inode_alloc, &bh, 0);\n        ocfs2_inode_lock_full_nested(inode, ...)\n            struct ocfs2_super *osb = OCFS2_SB(inode->i_sb);\n\nThus, a possible null-pointer dereference may occur.\n\nTo fix this bug, inode_alloc is checked on line 286.\n\nThis bug is found by a static analysis tool STCheck written by us.\n\nLink: http://lkml.kernel.org/r/20190726033717.32359-1-baijiaju1990@gmail.com\nSigned-off-by: Jia-Ju Bai <baijiaju1990@gmail.com>\nReviewed-by: Joseph Qi <joseph.qi@linux.alibaba.com>\nCc: Mark Fasheh <mark@fasheh.com>\nCc: Joel Becker <jlbec@evilplan.org>\nCc: Junxiao Bi <junxiao.bi@oracle.com>\nCc: Changwei Ge <gechangwei@live.cn>\nCc: Gang He <ghe@suse.com>\nCc: Jun Piao <piaojun@huawei.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Sasha Levin <sashal@kernel.org>","distinct":true,"url":"https://api.github.com/repos/Pzqqt/android_kernel_xiaomi_whyred/commits/23d94f1fec0aec5e547ae0c96c5da28d12fa652c"},{"sha":"7a5c21af789d6871de3f05185e221fb7eea6804b","author":{"name":"Thomas Bogendoerfer","email":"0a3f57713a24219f7eab806ed2a3e4f734d1b63f@suse.de"},"message":"MIPS: fw: sni: Fix out of bounds init of o32 stack\n\n[ Upstream commit efcb529694c3b707dc0471b312944337ba16e4dd ]\n\nUse ARRAY_SIZE to caluculate the top of the o32 stack.\n\nSigned-off-by: Thomas Bogendoerfer <tbogendoerfer@suse.de>\nSigned-off-by: Paul Burton <paul.burton@mips.com>\nCc: Ralf Baechle <ralf@linux-mips.org>\nCc: James Hogan <jhogan@kernel.org>\nCc: linux-mips@vger.kernel.org\nCc: linux-kernel@vger.kernel.org\nSigned-off-by: Sasha Levin <sashal@kernel.org>","distinct":true,"url":"https://api.github.com/repos/Pzqqt/android_kernel_xiaomi_whyred/commits/7a5c21af789d6871de3f05185e221fb7eea6804b"},{"sha":"e4cec9236988058b7e9cf5a57120c1e48c2108c6","author":{"name":"Chuck Lever","email":"e7d8216bf9b1956703857d0050bd04192118f43d@oracle.com"},"message":"NFSv4: Fix leak of clp->cl_acceptor string\n\n[ Upstream commit 1047ec868332034d1fbcb2fae19fe6d4cb869ff2 ]\n\nOur client can issue multiple SETCLIENTID operations to the same\nserver in some circumstances. Ensure that calls to\nnfs4_proc_setclientid() after the first one do not overwrite the\npreviously allocated cl_acceptor string.\n\nunreferenced object 0xffff888461031800 (size 32):\n  comm \"mount.nfs\", pid 2227, jiffies 4294822467 (age 1407.749s)\n  hex dump (first 32 bytes):\n    6e 66 73 40 6b 6c 69 6d 74 2e 69 62 2e 31 30 31  nfs@klimt.ib.101\n    35 67 72 61 6e 67 65 72 2e 6e 65 74 00 00 00 00  5granger.net....\n  backtrace:\n    [<00000000ab820188>] __kmalloc+0x128/0x176\n    [<00000000eeaf4ec8>] gss_stringify_acceptor+0xbd/0x1a7 [auth_rpcgss]\n    [<00000000e85e3382>] nfs4_proc_setclientid+0x34e/0x46c [nfsv4]\n    [<000000003d9cf1fa>] nfs40_discover_server_trunking+0x7a/0xed [nfsv4]\n    [<00000000b81c3787>] nfs4_discover_server_trunking+0x81/0x244 [nfsv4]\n    [<000000000801b55f>] nfs4_init_client+0x1b0/0x238 [nfsv4]\n    [<00000000977daf7f>] nfs4_set_client+0xfe/0x14d [nfsv4]\n    [<0000000053a68a2a>] nfs4_create_server+0x107/0x1db [nfsv4]\n    [<0000000088262019>] nfs4_remote_mount+0x2c/0x59 [nfsv4]\n    [<00000000e84a2fd0>] legacy_get_tree+0x2d/0x4c\n    [<00000000797e947c>] vfs_get_tree+0x20/0xc7\n    [<00000000ecabaaa8>] fc_mount+0xe/0x36\n    [<00000000f15fafc2>] vfs_kern_mount+0x74/0x8d\n    [<00000000a3ff4e26>] nfs_do_root_mount+0x8a/0xa3 [nfsv4]\n    [<00000000d1c2b337>] nfs4_try_mount+0x58/0xad [nfsv4]\n    [<000000004c9bddee>] nfs_fs_mount+0x820/0x869 [nfs]\n\nFixes: f11b2a1cfbf5 (\"nfs4: copy acceptor name from context ... \")\nSigned-off-by: Chuck Lever <chuck.lever@oracle.com>\nSigned-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>\nSigned-off-by: Sasha Levin <sashal@kernel.org>","distinct":true,"url":"https://api.github.com/repos/Pzqqt/android_kernel_xiaomi_whyred/commits/e4cec9236988058b7e9cf5a57120c1e48c2108c6"}]}
{"actor":{"display_login":"Pzqqt"}}