{"push_id":4489439505,"size":1000,"distinct_size":14904,"ref":"refs/heads/torvalds","head":"6327edceb62bc4c91195e2dc6d5574a53005cb5a","before":"219d54332a09e8d8741c1e1982f5eae56099de85","commits":[{"sha":"96dd4bcbac8ab5164ec3f07f9ae1f1611e767417","author":{"name":"Olof Johansson","email":"8c69ee23f3f44f8162a64d579c1fa25c2f55298a@lixom.net"},"message":"Merge tag 'arm-soc/for-5.5/devicetree-fixes' of https://github.com/Broadcom/stblinux into arm/fixes\n\nThis pull request contains Broadcom ARM-based SoCs Device Tree fixes for\nv5.5-rc1, please pull the following:\n\n- Nicolas fixes the SoC's dma-range property to cover the full 1GB\n  aperture\n\n- Stefan fixes the critical temperature trip point to be set before the\n  firmware performs thermal throttling\n\n- Florian fixes the BCM5301X and Cygnus MDIO nodes to have corrected\n  #address-cells and #size-cells properties\n\n* tag 'arm-soc/for-5.5/devicetree-fixes' of https://github.com/Broadcom/stblinux:\n  ARM: dts: bcm283x: Fix critical trip point\n  ARM: dts: Cygnus: Fix MDIO node address/size cells\n  ARM: dts: bcm2711: fix soc's node dma-ranges\n  ARM: dts: BCM5301X: Fix MDIO node address/size cells\n\nLink: https://lore.kernel.org/r/20191210205850.12442-1-f.fainelli@gmail.com\nSigned-off-by: Olof Johansson <olof@lixom.net>","distinct":true,"url":"https://api.github.com/repos/s-moch/linux-saa716x/commits/96dd4bcbac8ab5164ec3f07f9ae1f1611e767417"},{"sha":"9103bb419aef8b908a169ebed0e1c16ae060576a","author":{"name":"Olof Johansson","email":"8c69ee23f3f44f8162a64d579c1fa25c2f55298a@lixom.net"},"message":"Merge tag 'reset-fixes-for-v5.5-2' of git://git.pengutronix.de/git/pza/linux into arm/fixes\n\nReset controller fixes for v5.5, part 2\n\nFix the example in the brcmstb-reset device tree bindings, remove a bogus\nresource alignment check from the reset-brcmstb driver, fix the documented\nreturn value type for the reset_control_array_get functions, and fix a\ndevres memory leak when requesting optional, not present reset controls.\n\n* tag 'reset-fixes-for-v5.5-2' of git://git.pengutronix.de/git/pza/linux:\n  reset: Do not register resource data for missing resets\n  reset: Fix {of,devm}_reset_control_array_get kerneldoc return types\n  reset: brcmstb: Remove resource checks\n  dt-bindings: reset: Fix brcmstb-reset example\n\nLink: https://lore.kernel.org/r/bb59b9f83892aa3c876f5da87890b0496f2dc755.camel@pengutronix.de\nSigned-off-by: Olof Johansson <olof@lixom.net>","distinct":true,"url":"https://api.github.com/repos/s-moch/linux-saa716x/commits/9103bb419aef8b908a169ebed0e1c16ae060576a"},{"sha":"158d58335393af3956a9c06f0816ee75ed1f1447","author":{"name":"David Howells","email":"ebac1d06c1688626821bb0e574a037a7a5354e49@redhat.com"},"message":"afs: Fix mountpoint parsing\n\nEach AFS mountpoint has strings that define the target to be mounted.  This\nis required to end in a dot that is supposed to be stripped off.  The\nstring can include suffixes of \".readonly\" or \".backup\" - which are\nsupposed to come before the terminal dot.  To add to the confusion, the \"fs\nlsmount\" afs utility does not show the terminal dot when displaying the\nstring.\n\nThe kernel mount source string parser, however, assumes that the terminal\ndot marks the suffix and that the suffix is always \"\" and is thus ignored.\nIn most cases, there is no suffix and this is not a problem - but if there\nis a suffix, it is lost and this affects the ability to mount the correct\nvolume.\n\nThe command line mount command, on the other hand, is expected not to\ninclude a terminal dot - so the problem doesn't arise there.\n\nFix this by making sure that the dot exists and then stripping it when\npassing the string to the mount configuration.\n\nFixes: bec5eb614130 (\"AFS: Implement an autocell mount capability [ver #2]\")\nReported-by: Jonathan Billings <jsbillings@jsbillings.org>\nSigned-off-by: David Howells <dhowells@redhat.com>\nReviewed-by: Marc Dionne <marc.dionne@auristor.com>\nTested-by: Jonathan Billings <jsbillings@jsbillings.org>","distinct":true,"url":"https://api.github.com/repos/s-moch/linux-saa716x/commits/158d58335393af3956a9c06f0816ee75ed1f1447"},{"sha":"3a019636e6b00997594f91339411fa6bbd2c6d33","author":{"name":"Michael Ellerman","email":"864f124608374e06e4da1fa5d2e47ed839b95411@ellerman.id.au"},"message":"selftests: Fix dangling documentation references to kselftest_module.sh\n\nCommit c78fd76f2b67 (\"selftests: Move kselftest_module.sh into\nkselftest/\") moved kselftest_module.sh but missed updating a few\nreferences to the path in documentation.\n\nFixes: c78fd76f2b67 (\"selftests: Move kselftest_module.sh into kselftest/\")\nSigned-off-by: Michael Ellerman <mpe@ellerman.id.au>\nAcked-by: Kees Cook <keescook@chromium.org>\nSigned-off-by: Shuah Khan <skhan@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/s-moch/linux-saa716x/commits/3a019636e6b00997594f91339411fa6bbd2c6d33"},{"sha":"d187801d1a46519d2a322f879f7c8f85c685372e","author":{"name":"SeongJae Park","email":"fa6560980a3e249c428de5cde4d536aa0eda55fa@amazon.de"},"message":"kselftest/runner: Print new line in print of timeout log\n\nIf a timeout failure occurs, kselftest kills the test process and prints\nthe timeout log.  If the test process has killed while printing a log\nthat ends with new line, the timeout log can be printed in middle of the\ntest process output so that it can be seems like a comment, as below:\n\n    # test_process_log\tnot ok 3 selftests: timers: nsleep-lat # TIMEOUT\n\nThis commit avoids such problem by printing one more line before the\nTIMEOUT failure log.\n\nSigned-off-by: SeongJae Park <sjpark@amazon.de>\nAcked-by: Kees Cook <keescook@chromium.org>\nSigned-off-by: Shuah Khan <skhan@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/s-moch/linux-saa716x/commits/d187801d1a46519d2a322f879f7c8f85c685372e"},{"sha":"4eac734486fd431e0756cc5e929f140911a36a53","author":{"name":"SeongJae Park","email":"fa6560980a3e249c428de5cde4d536aa0eda55fa@amazon.de"},"message":"kselftest: Support old perl versions\n\nOn an old perl such as v5.10.1, `kselftest/prefix.pl` gives below error\nmessage:\n\n    Can't locate object method \"autoflush\" via package \"IO::Handle\" at kselftest/prefix.pl line 10.\n\nThis commit fixes the error by explicitly specifying the use of the\n`IO::Handle` package.\n\nSigned-off-by: SeongJae Park <sjpark@amazon.de>\nAcked-by: Kees Cook <keescook@chromium.org>\nSigned-off-by: Shuah Khan <skhan@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/s-moch/linux-saa716x/commits/4eac734486fd431e0756cc5e929f140911a36a53"},{"sha":"1da4bd9f9d187f53618890d7b66b9628bbec3c70","author":{"name":"David Howells","email":"ebac1d06c1688626821bb0e574a037a7a5354e49@redhat.com"},"message":"afs: Fix creation calls in the dynamic root to fail with EOPNOTSUPP\n\nFix the lookup method on the dynamic root directory such that creation\ncalls, such as mkdir, open(O_CREAT), symlink, etc. fail with EOPNOTSUPP\nrather than failing with some odd error (such as EEXIST).\n\nlookup() itself tries to create automount directories when it is invoked.\nThese are cached locally in RAM and not committed to storage.\n\nSigned-off-by: David Howells <dhowells@redhat.com>\nReviewed-by: Marc Dionne <marc.dionne@auristor.com>\nTested-by: Jonathan Billings <jsbillings@jsbillings.org>","distinct":true,"url":"https://api.github.com/repos/s-moch/linux-saa716x/commits/1da4bd9f9d187f53618890d7b66b9628bbec3c70"},{"sha":"106bc79843c3c6f4f00753d1f46e54e815f99377","author":{"name":"David Howells","email":"ebac1d06c1688626821bb0e574a037a7a5354e49@redhat.com"},"message":"afs: Fix missing cell comparison in afs_test_super()\n\nFix missing cell comparison in afs_test_super().  Without this, any pair\nvolumes that have the same volume ID will share a superblock, no matter the\ncell, unless they're in different network namespaces.\n\nNormally, most users will only deal with a single cell and so they won't\nsee this.  Even if they do look into a second cell, they won't see a\nproblem unless they happen to hit a volume with the same ID as one they've\nalready got mounted.\n\nBefore the patch:\n\n    # ls /afs/grand.central.org/archive\n    linuxdev/  mailman/  moin/  mysql/  pipermail/  stage/  twiki/\n    # ls /afs/kth.se/\n    linuxdev/  mailman/  moin/  mysql/  pipermail/  stage/  twiki/\n    # cat /proc/mounts | grep afs\n    none /afs afs rw,relatime,dyn,autocell 0 0\n    #grand.central.org:root.cell /afs/grand.central.org afs ro,relatime 0 0\n    #grand.central.org:root.archive /afs/grand.central.org/archive afs ro,relatime 0 0\n    #grand.central.org:root.archive /afs/kth.se afs ro,relatime 0 0\n\nAfter the patch:\n\n    # ls /afs/grand.central.org/archive\n    linuxdev/  mailman/  moin/  mysql/  pipermail/  stage/  twiki/\n    # ls /afs/kth.se/\n    admin/        common/  install/  OldFiles/  service/  system/\n    bakrestores/  home/    misc/     pkg/       src/      wsadmin/\n    # cat /proc/mounts | grep afs\n    none /afs afs rw,relatime,dyn,autocell 0 0\n    #grand.central.org:root.cell /afs/grand.central.org afs ro,relatime 0 0\n    #grand.central.org:root.archive /afs/grand.central.org/archive afs ro,relatime 0 0\n    #kth.se:root.cell /afs/kth.se afs ro,relatime 0 0\n\nFixes: ^1da177e4c3f4 (\"Linux-2.6.12-rc2\")\nReported-by: Carsten Jacobi <jacobi@de.ibm.com>\nSigned-off-by: David Howells <dhowells@redhat.com>\nReviewed-by: Marc Dionne <marc.dionne@auristor.com>\nTested-by: Jonathan Billings <jsbillings@jsbillings.org>\ncc: Todd DeSantis <atd@us.ibm.com>","distinct":true,"url":"https://api.github.com/repos/s-moch/linux-saa716x/commits/106bc79843c3c6f4f00753d1f46e54e815f99377"},{"sha":"50559800b76a7a2a46da303100da639536261808","author":{"name":"David Howells","email":"ebac1d06c1688626821bb0e574a037a7a5354e49@redhat.com"},"message":"afs: Show volume name in /proc/net/afs/<cell>/volumes\n\nShow the name of each volume in /proc/net/afs/<cell>/volumes to make it\neasier to work out the name corresponding to a volume ID.  This makes it\neasier to work out which mounts in /proc/mounts correspond to which volume\nID.\n\nSigned-off-by: David Howells <dhowells@redhat.com>\nReviewed-by: Marc Dionne <marc.dionne@auristor.com>","distinct":true,"url":"https://api.github.com/repos/s-moch/linux-saa716x/commits/50559800b76a7a2a46da303100da639536261808"},{"sha":"a7ede3d16808b8f3915c8572d783530a82b2f027","author":{"name":"Guoqing Jiang","email":"2c37d25cb7af72517b3f826be5c363cdace8c60f@cloud.ionos.com"},"message":"raid5: need to set STRIPE_HANDLE for batch head\n\nWith commit 6ce220dd2f8ea71d6afc29b9a7524c12e39f374a (\"raid5: don't set\nSTRIPE_HANDLE to stripe which is in batch list\"), we don't want to set\nSTRIPE_HANDLE flag for sh which is already in batch list.\n\nHowever, the stripe which is the head of batch list should set this flag,\notherwise panic could happen inside init_stripe at BUG_ON(sh->batch_head),\nit is reproducible with raid5 on top of nvdimm devices per Xiao oberserved.\n\nThanks for Xiao's effort to verify the change.\n\nFixes: 6ce220dd2f8ea (\"raid5: don't set STRIPE_HANDLE to stripe which is in batch list\")\nReported-by: Xiao Ni <xni@redhat.com>\nTested-by: Xiao Ni <xni@redhat.com>\nSigned-off-by: Guoqing Jiang <guoqing.jiang@cloud.ionos.com>\nSigned-off-by: Song Liu <songliubraving@fb.com>","distinct":true,"url":"https://api.github.com/repos/s-moch/linux-saa716x/commits/a7ede3d16808b8f3915c8572d783530a82b2f027"},{"sha":"028288df635f5a9addd48ac4677b720192747944","author":{"name":"Zhiqiang Liu","email":"4be84e159123a695400200fa64ce9dbcc2b01654@huawei.com"},"message":"md: raid1: check rdev before reference in raid1_sync_request func\n\nIn raid1_sync_request func, rdev should be checked before reference.\n\nSigned-off-by: Zhiqiang Liu <liuzhiqiang26@huawei.com>\nSigned-off-by: Song Liu <songliubraving@fb.com>","distinct":true,"url":"https://api.github.com/repos/s-moch/linux-saa716x/commits/028288df635f5a9addd48ac4677b720192747944"},{"sha":"3b7436cc9449d5ff7fa1c1fd5bc3edb6402ff5b8","author":{"name":"Yufen Yu","email":"d1110ad58a5ddf80c0af1d3b9cbe70359fc7e0e3@huawei.com"},"message":"md: make sure desc_nr less than MD_SB_DISKS\n\nFor super_90_load, we need to make sure 'desc_nr' less\nthan MD_SB_DISKS, avoiding invalid memory access of 'sb->disks'.\n\nFixes: 228fc7d76db6 (\"md: avoid invalid memory access for array sb->dev_roles\")\nSigned-off-by: Yufen Yu <yuyufen@huawei.com>\nSigned-off-by: Song Liu <songliubraving@fb.com>","distinct":true,"url":"https://api.github.com/repos/s-moch/linux-saa716x/commits/3b7436cc9449d5ff7fa1c1fd5bc3edb6402ff5b8"},{"sha":"b62b6cf170237677ae96001940c54d5c09d0015a","author":{"name":"Vasily Gorbik","email":"fd6608149f5f589003abf198bcd5ef1b94afa26b@linux.ibm.com"},"message":"s390/spinlock: remove confusing comment in arch_spin_lock_wait\n\narch_spin_lock_wait does not take steal time into consideration.\n\nSigned-off-by: Vasily Gorbik <gor@linux.ibm.com>","distinct":true,"url":"https://api.github.com/repos/s-moch/linux-saa716x/commits/b62b6cf170237677ae96001940c54d5c09d0015a"},{"sha":"7e914fd17e9a750d8896e5645c84e75e52d77a4b","author":{"name":"Colin Ian King","email":"d100aa70785e45ee8deab668147d941941915c21@canonical.com"},"message":"s390/test_unwind: fix spelling mistake \"reqister\" -> \"register\"\n\nThere is a spelling mistake in a pr_info message. Fix it.\n\nLink: https://lkml.kernel.org/r/20191202090215.28766-1-colin.king@canonical.com\nSigned-off-by: Colin Ian King <colin.king@canonical.com>\nSigned-off-by: Vasily Gorbik <gor@linux.ibm.com>","distinct":true,"url":"https://api.github.com/repos/s-moch/linux-saa716x/commits/7e914fd17e9a750d8896e5645c84e75e52d77a4b"},{"sha":"39d4a501a9ef55c57b51e3ef07fc2aeed7f30b3b","author":{"name":"Thomas Richter","email":"8efd8ac704d21550d1708b5fda9fd8afae04d143@linux.ibm.com"},"message":"s390/cpum_sf: Adjust sampling interval to avoid hitting sample limits\n\nFunction perf_event_ever_overflow() and perf_event_account_interrupt()\nare called every time samples are processed by the interrupt handler.\nHowever function perf_event_account_interrupt() has checks to avoid being\nflooded with interrupts (more then 1000 samples are received per\ntask_tick).  Samples are then dropped and a PERF_RECORD_THROTTLED is\nadded to the perf data. The perf subsystem limit calculation is:\n\n    maximum sample frequency := 100000 --> 1 samples per 10 us\n    task_tick = 10ms = 10000us --> 1000 samples per task_tick\n\nThe work flow is\n\nmeasurement_alert() uses SDBT head and each SBDT points to 511\n SDB pages, each with 126 sample entries. After processing 8 SBDs\n and for each valid sample calling:\n\n     perf_event_overflow()\n       perf_event_account_interrupts()\n\nthere is a considerable amount of samples being dropped, especially when\nthe sample frequency is very high and near the 100000 limit.\n\nTo avoid the high amount of samples being dropped near the end of a\ntask_tick time frame, increment the sampling interval in case of\ndropped events. The CPU Measurement sampling facility on the s390\nsupports only intervals, specifiing how many CPU cycles have to be\nexecuted before a sample is generated. Increase the interval when the\nsamples being generated hit the task_tick limit.\n\nSigned-off-by: Thomas Richter <tmricht@linux.ibm.com>\nSigned-off-by: Vasily Gorbik <gor@linux.ibm.com>","distinct":true,"url":"https://api.github.com/repos/s-moch/linux-saa716x/commits/39d4a501a9ef55c57b51e3ef07fc2aeed7f30b3b"},{"sha":"0539ad0b22877225095d8adef0c376f52cc23834","author":{"name":"Thomas Richter","email":"8efd8ac704d21550d1708b5fda9fd8afae04d143@linux.ibm.com"},"message":"s390/cpum_sf: Avoid SBD overflow condition in irq handler\n\nThe s390 CPU Measurement sampling facility has an overflow condition\nwhich fires when all entries in a SBD are used.\nThe measurement alert interrupt is triggered and reads out all samples\nin this SDB. It then tests the successor SDB, if this SBD is not full,\nthe interrupt handler does not read any samples at all from this SDB\nThe design waits for the hardware to fill this SBD and then trigger\nanother meassurement alert interrupt.\n\nThis scheme works nicely until\nan perf_event_overflow() function call discards the sample due to\na too high sampling rate.\nThe interrupt handler has logic to read out a partially filled SDB\nwhen the perf event overflow condition in linux common code is met.\nThis causes the CPUM sampling measurement hardware and the PMU\ndevice driver to operate on the same SBD's trailer entry.\nThis should not happen.\n\nThis can be seen here using this trace:\n   cpumsf_pmu_add: tear:0xb5286000\n   hw_perf_event_update: sdbt 0xb5286000 full 1 over 0 flush_all:0\n   hw_perf_event_update: sdbt 0xb5286008 full 0 over 0 flush_all:0\n        above shows 1. interrupt\n   hw_perf_event_update: sdbt 0xb5286008 full 1 over 0 flush_all:0\n   hw_perf_event_update: sdbt 0xb5286008 full 0 over 0 flush_all:0\n        above shows 2. interrupt\n\t... this goes on fine until...\n   hw_perf_event_update: sdbt 0xb5286068 full 1 over 0 flush_all:0\n   perf_push_sample1: overflow\n      one or more samples read from the IRQ handler are rejected by\n      perf_event_overflow() and the IRQ handler advances to the next SDB\n      and modifies the trailer entry of a partially filled SDB.\n   hw_perf_event_update: sdbt 0xb5286070 full 0 over 0 flush_all:1\n      timestamp: 14:32:52.519953\n\nNext time the IRQ handler is called for this SDB the trailer entry shows\nan overflow count of 19 missed entries.\n   hw_perf_event_update: sdbt 0xb5286070 full 1 over 19 flush_all:1\n      timestamp: 14:32:52.970058\n\nRemove access to a follow on SDB when event overflow happened.\n\nSigned-off-by: Thomas Richter <tmricht@linux.ibm.com>\nSigned-off-by: Vasily Gorbik <gor@linux.ibm.com>","distinct":true,"url":"https://api.github.com/repos/s-moch/linux-saa716x/commits/0539ad0b22877225095d8adef0c376f52cc23834"},{"sha":"157309a97015d8b32d65847d8a6d493d1a958e93","author":{"name":"Christian Borntraeger","email":"49712f635b03c16d7f4c43df70e49ec8c565813d@de.ibm.com"},"message":"s390/uv: use EOPNOTSUPP instead of ENOTSUPP\n\nENOTSUP is just an internal kernel error and should never reach\nuserspace. The return value of the share function is not exported to\nuserspace, but to avoid giving bad examples let us use EOPNOTSUPP:\n\nSuggested-by: Heiko Carstens <heiko.carstens@de.ibm.com>\nAcked-by: Janosch Frank <frankja@linux.ibm.com>\nSigned-off-by: Christian Borntraeger <borntraeger@de.ibm.com>\nSigned-off-by: Vasily Gorbik <gor@linux.ibm.com>","distinct":true,"url":"https://api.github.com/repos/s-moch/linux-saa716x/commits/157309a97015d8b32d65847d8a6d493d1a958e93"},{"sha":"1b68ac8678a8e9993deebd55014cbe803e78ca02","author":{"name":"Heiko Carstens","email":"8dcf0f69152f32f23184f83357a3731522e56b9c@de.ibm.com"},"message":"s390: remove last diag 0x44 caller\n\ndiag 0x44 is a voluntary undirected yield of a virtual CPU. This has\ncaused a lot of performance issues in the past.\n\nThere is only one caller left, and that one is only executed if diag\n0x9c (directed yield) is not present. Given that all hypervisors\nimplement diag 0x9c anyway, remove the last diag 0x44 to avoid that\nmore callers will be added.\n\nWorst case that could happen now, if diag 0x9c is not present, is that\na virtual CPU would loop a bit instead of giving its time slice up.\n\ndiag 0x44 statistics in debugfs are kept and will always be zero, so\nthat user space can tell that there are no calls.\n\nSigned-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>\nSigned-off-by: Vasily Gorbik <gor@linux.ibm.com>","distinct":true,"url":"https://api.github.com/repos/s-moch/linux-saa716x/commits/1b68ac8678a8e9993deebd55014cbe803e78ca02"},{"sha":"3e39ce266a273e5751e5792aee248cb8d9630c8b","author":{"name":"Vasily Gorbik","email":"fd6608149f5f589003abf198bcd5ef1b94afa26b@linux.ibm.com"},"message":"s390/kasan: add KASAN_VMALLOC support\n\nAdd KASAN_VMALLOC support which now enables vmalloc memory area access\nchecks as well as enables usage of VMAP_STACK under kasan.\n\nKASAN_VMALLOC changes the way vmalloc and modules areas shadow memory\nis handled. With this new approach only top level page tables are\npre-populated and lower levels are filled dynamically upon memory\nallocation.\n\nAcked-by: Ilya Leoshkevich <iii@linux.ibm.com>\nSigned-off-by: Vasily Gorbik <gor@linux.ibm.com>","distinct":true,"url":"https://api.github.com/repos/s-moch/linux-saa716x/commits/3e39ce266a273e5751e5792aee248cb8d9630c8b"},{"sha":"02cca5769f5e07748c839168dc0b5f21bbacff08","author":{"name":"Tianci.Yin","email":"c9650fea3c32d97506949dbd3efda5bf6dcefa07@amd.com"},"message":"drm/amdgpu/gfx10: update gfx golden settings\n\nadd registers: mmSPI_CONFIG_CNTL\n\nReviewed-by: Feifei Xu <Feifei.Xu@amd.com>\nSigned-off-by: Tianci.Yin <tianci.yin@amd.com>\nSigned-off-by: Alex Deucher <alexander.deucher@amd.com>","distinct":true,"url":"https://api.github.com/repos/s-moch/linux-saa716x/commits/02cca5769f5e07748c839168dc0b5f21bbacff08"}]}
{"actor":{"display_login":"s-moch"}}