{"push_id":2866545028,"size":310,"distinct_size":310,"ref":"refs/heads/master","head":"11da3a7f84f19c26da6f86af878298694ede0804","before":"57361846b52bc686112da6ca5368d11210796804","commits":[{"sha":"f623f75ae443d0c771635d51cc986b9d389bf631","author":{"name":"Arnd Bergmann","email":"f2c659f01951776204a6c5b902787d9019fbeebd@arndb.de"},"message":"rfkill-gpio: include linux/mod_devicetable.h\n\nOne more driver is apparently broken by the recent change\nto linux/platform_device.h:\n\nnet/rfkill/rfkill-gpio.c: In function 'rfkill_gpio_acpi_probe':\nnet/rfkill/rfkill-gpio.c:82:29: error: dereferencing pointer to incomplete type 'const struct acpi_device_id'\n\nInclude linux/mod_devicetable.h to get the definition of the\nacpi_device_id structure.\n\nFixes: ac3167257b9f (\"headers: separate linux/mod_devicetable.h from linux/platform_device.h\")\nSigned-off-by: Arnd Bergmann <arnd@arndb.de>\nSigned-off-by: Johannes Berg <johannes.berg@intel.com>","distinct":true,"url":"https://api.github.com/repos/woodsts/linux-stable/commits/f623f75ae443d0c771635d51cc986b9d389bf631"},{"sha":"77cfaf52eca5cac30ed029507e0cab065f888995","author":{"name":"Toke Høiland-Jørgensen","email":"c739cf9ea9032889618db8b95a03da66fcc9867e@toke.dk"},"message":"mac80211: Run TXQ teardown code before de-registering interfaces\n\nThe TXQ teardown code can reference the vif data structures that are\nstored in the netdev private memory area if there are still packets on\nthe queue when it is being freed. Since the TXQ teardown code is run\nafter the netdevs are freed, this can lead to a use-after-free. Fix this\nby moving the TXQ teardown code to earlier in ieee80211_unregister_hw().\n\nReported-by: Ben Greear <greearb@candelatech.com>\nTested-by: Ben Greear <greearb@candelatech.com>\nSigned-off-by: Toke Høiland-Jørgensen <toke@toke.dk>\nSigned-off-by: Johannes Berg <johannes.berg@intel.com>","distinct":true,"url":"https://api.github.com/repos/woodsts/linux-stable/commits/77cfaf52eca5cac30ed029507e0cab065f888995"},{"sha":"c066fafc595eef5ae3c83ae3a8305956b8c3ef15","author":{"name":"Paul Mackerras","email":"19a0ba370c443ba08d20b5061586430ab449ee8c@ozlabs.org"},"message":"KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix()\n\nSince commit e641a317830b (\"KVM: PPC: Book3S HV: Unify dirty page map\nbetween HPT and radix\", 2017-10-26), kvm_unmap_radix() computes the\nnumber of PAGE_SIZEd pages being unmapped and passes it to\nkvmppc_update_dirty_map(), which expects to be passed the page size\ninstead.  Consequently it will only mark one system page dirty even\nwhen a large page (for example a THP page) is being unmapped.  The\nconsequence of this is that part of the THP page might not get copied\nduring live migration, resulting in memory corruption for the guest.\n\nThis fixes it by computing and passing the page size in kvm_unmap_radix().\n\nCc: stable@vger.kernel.org # v4.15+\nFixes: e641a317830b (KVM: PPC: Book3S HV: Unify dirty page map between HPT and radix)\nSigned-off-by: Paul Mackerras <paulus@ozlabs.org>","distinct":true,"url":"https://api.github.com/repos/woodsts/linux-stable/commits/c066fafc595eef5ae3c83ae3a8305956b8c3ef15"},{"sha":"484004339d4514fde425f6e8a9f6a6cc979bb0c3","author":{"name":"Johannes Berg","email":"bff32994ff0f8d048f262a8388145a71b6071bfe@intel.com"},"message":"mac80211_hwsim: require at least one channel\n\nSyzbot continues to try to create mac80211_hwsim radios, and\nmanages to pass parameters that are later checked with WARN_ON\nin cfg80211 - catch another one in hwsim directly.\n\nReported-by: syzbot+2a12f11c306afe871c1f@syzkaller.appspotmail.com\nSigned-off-by: Johannes Berg <johannes.berg@intel.com>","distinct":true,"url":"https://api.github.com/repos/woodsts/linux-stable/commits/484004339d4514fde425f6e8a9f6a6cc979bb0c3"},{"sha":"8ecebf4d767e2307a946c8905278d6358eda35c3","author":{"name":"Robbie Ko","email":"3e8473ebda093339b57e9fa2dd0b2ba18a79d878@synology.com"},"message":"Btrfs: fix unexpected failure of nocow buffered writes after snapshotting when low on space\n\nCommit e9894fd3e3b3 (\"Btrfs: fix snapshot vs nocow writting\") forced\nnocow writes to fallback to COW, during writeback, when a snapshot is\ncreated. This resulted in writes made before creating the snapshot to\nunexpectedly fail with ENOSPC during writeback when success (0) was\nreturned to user space through the write system call.\n\nThe steps leading to this problem are:\n\n1. When it's not possible to allocate data space for a write, the\n   buffered write path checks if a NOCOW write is possible.  If it is,\n   it will not reserve space and success (0) is returned to user space.\n\n2. Then when a snapshot is created, the root's will_be_snapshotted\n   atomic is incremented and writeback is triggered for all inode's that\n   belong to the root being snapshotted. Incrementing that atomic forces\n   all previous writes to fallback to COW during writeback (running\n   delalloc).\n\n3. This results in the writeback for the inodes to fail and therefore\n   setting the ENOSPC error in their mappings, so that a subsequent\n   fsync on them will report the error to user space. So it's not a\n   completely silent data loss (since fsync will report ENOSPC) but it's\n   a very unexpected and undesirable behaviour, because if a clean\n   shutdown/unmount of the filesystem happens without previous calls to\n   fsync, it is expected to have the data present in the files after\n   mounting the filesystem again.\n\nSo fix this by adding a new atomic named snapshot_force_cow to the\nroot structure which prevents this behaviour and works the following way:\n\n1. It is incremented when we start to create a snapshot after triggering\n   writeback and before waiting for writeback to finish.\n\n2. This new atomic is now what is used by writeback (running delalloc)\n   to decide whether we need to fallback to COW or not. Because we\n   incremented this new atomic after triggering writeback in the\n   snapshot creation ioctl, we ensure that all buffered writes that\n   happened before snapshot creation will succeed and not fallback to\n   COW (which would make them fail with ENOSPC).\n\n3. The existing atomic, will_be_snapshotted, is kept because it is used\n   to force new buffered writes, that start after we started\n   snapshotting, to reserve data space even when NOCOW is possible.\n   This makes these writes fail early with ENOSPC when there's no\n   available space to allocate, preventing the unexpected behaviour of\n   writeback later failing with ENOSPC due to a fallback to COW mode.\n\nFixes: e9894fd3e3b3 (\"Btrfs: fix snapshot vs nocow writting\")\nSigned-off-by: Robbie Ko <robbieko@synology.com>\nReviewed-by: Filipe Manana <fdmanana@suse.com>\nSigned-off-by: David Sterba <dsterba@suse.com>","distinct":true,"url":"https://api.github.com/repos/woodsts/linux-stable/commits/8ecebf4d767e2307a946c8905278d6358eda35c3"},{"sha":"46dec40fb741f00f1864580130779aeeaf24fb3d","author":{"name":"Paul Mackerras","email":"19a0ba370c443ba08d20b5061586430ab449ee8c@ozlabs.org"},"message":"KVM: PPC: Book3S HV: Don't truncate HPTE index in xlate function\n\nThis fixes a bug which causes guest virtual addresses to get translated\nto guest real addresses incorrectly when the guest is using the HPT MMU\nand has more than 256GB of RAM, or more specifically has a HPT larger\nthan 2GB.  This has showed up in testing as a failure of the host to\nemulate doorbell instructions correctly on POWER9 for HPT guests with\nmore than 256GB of RAM.\n\nThe bug is that the HPTE index in kvmppc_mmu_book3s_64_hv_xlate()\nis stored as an int, and in forming the HPTE address, the index gets\nshifted left 4 bits as an int before being signed-extended to 64 bits.\nThe simple fix is to make the variable a long int, matching the\nreturn type of kvmppc_hv_find_lock_hpte(), which is what calculates\nthe index.\n\nFixes: 697d3899dcb4 (\"KVM: PPC: Implement MMIO emulation support for Book3S HV guests\")\nSigned-off-by: Paul Mackerras <paulus@ozlabs.org>","distinct":true,"url":"https://api.github.com/repos/woodsts/linux-stable/commits/46dec40fb741f00f1864580130779aeeaf24fb3d"},{"sha":"8a54d8fc160e67ad485d95a0322ce1221f80770a","author":{"name":"Johannes Berg","email":"bff32994ff0f8d048f262a8388145a71b6071bfe@intel.com"},"message":"cfg80211: remove division by size of sizeof(struct ieee80211_wmm_rule)\n\nPointer arithmetic already adjusts by the size of the struct,\nso the sizeof() calculation is wrong. This is basically the\nsame as Colin King's patch for similar code in the iwlwifi\ndriver.\n\nFixes: 230ebaa189af (\"cfg80211: read wmm rules from regulatory database\")\nSigned-off-by: Johannes Berg <johannes.berg@intel.com>","distinct":true,"url":"https://api.github.com/repos/woodsts/linux-stable/commits/8a54d8fc160e67ad485d95a0322ce1221f80770a"},{"sha":"d4682ba03ef618b6ef4be7cedc7aacaf505d3a58","author":{"name":"Filipe Manana","email":"e0fcd583df77ec6c08e6d1257619cc1216ddc994@suse.com"},"message":"Btrfs: sync log after logging new name\n\nWhen we add a new name for an inode which was logged in the current\ntransaction, we update the inode in the log so that its new name and\nancestors are added to the log. However when we do this we do not persist\nthe log, so the changes remain in memory only, and as a consequence, any\nancestors that were created in the current transaction are updated such\nthat future calls to btrfs_inode_in_log() return true. This leads to a\nsubsequent fsync against such new ancestor directories returning\nimmediately, without persisting the log, therefore after a power failure\nthe new ancestor directories do not exist, despite fsync being called\nagainst them explicitly.\n\nExample:\n\n  $ mkfs.btrfs -f /dev/sdb\n  $ mount /dev/sdb /mnt\n\n  $ mkdir /mnt/A\n  $ mkdir /mnt/B\n  $ mkdir /mnt/A/C\n  $ touch /mnt/B/foo\n  $ xfs_io -c \"fsync\" /mnt/B/foo\n  $ ln /mnt/B/foo /mnt/A/C/foo\n  $ xfs_io -c \"fsync\" /mnt/A\n  <power failure>\n\nAfter the power failure, directory \"A\" does not exist, despite the explicit\nfsync on it.\n\nInstead of fixing this by changing the behaviour of the explicit fsync on\ndirectory \"A\" to persist the log instead of doing nothing, make the logging\nof the new file name (which happens when creating a hard link or renaming)\npersist the log. This approach not only is simpler, not requiring addition\nof new fields to the inode in memory structure, but also gives us the same\nbehaviour as ext4, xfs and f2fs (possibly other filesystems too).\n\nA test case for fstests follows soon.\n\nFixes: 12fcfd22fe5b (\"Btrfs: tree logging unlink/rename fixes\")\nReported-by: Vijay Chidambaram <vvijay03@gmail.com>\nSigned-off-by: Filipe Manana <fdmanana@suse.com>\nSigned-off-by: David Sterba <dsterba@suse.com>","distinct":true,"url":"https://api.github.com/repos/woodsts/linux-stable/commits/d4682ba03ef618b6ef4be7cedc7aacaf505d3a58"},{"sha":"de02b9f6bb65a6a1848f346f7a3617b7a9b930c0","author":{"name":"Filipe Manana","email":"e0fcd583df77ec6c08e6d1257619cc1216ddc994@suse.com"},"message":"Btrfs: fix data corruption when deduplicating between different files\n\nIf we deduplicate extents between two different files we can end up\ncorrupting data if the source range ends at the size of the source file,\nthe source file's size is not aligned to the filesystem's block size\nand the destination range does not go past the size of the destination\nfile size.\n\nExample:\n\n  $ mkfs.btrfs -f /dev/sdb\n  $ mount /dev/sdb /mnt\n\n  $ xfs_io -f -c \"pwrite -S 0x6b 0 2518890\" /mnt/foo\n  # The first byte with a value of 0xae starts at an offset (2518890)\n  # which is not a multiple of the sector size.\n  $ xfs_io -c \"pwrite -S 0xae 2518890 102398\" /mnt/foo\n\n  # Confirm the file content is full of bytes with values 0x6b and 0xae.\n  $ od -t x1 /mnt/foo\n  0000000 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b\n  *\n  11467540 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b ae ae ae ae ae ae\n  11467560 ae ae ae ae ae ae ae ae ae ae ae ae ae ae ae ae\n  *\n  11777540 ae ae ae ae ae ae ae ae\n  11777550\n\n  # Create a second file with a length not aligned to the sector size,\n  # whose bytes all have the value 0x6b, so that its extent(s) can be\n  # deduplicated with the first file.\n  $ xfs_io -f -c \"pwrite -S 0x6b 0 557771\" /mnt/bar\n\n  # Now deduplicate the entire second file into a range of the first file\n  # that also has all bytes with the value 0x6b. The destination range's\n  # end offset must not be aligned to the sector size and must be less\n  # then the offset of the first byte with the value 0xae (byte at offset\n  # 2518890).\n  $ xfs_io -c \"dedupe /mnt/bar 0 1957888 557771\" /mnt/foo\n\n  # The bytes in the range starting at offset 2515659 (end of the\n  # deduplication range) and ending at offset 2519040 (start offset\n  # rounded up to the block size) must all have the value 0xae (and not\n  # replaced with 0x00 values). In other words, we should have exactly\n  # the same data we had before we asked for deduplication.\n  $ od -t x1 /mnt/foo\n  0000000 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b\n  *\n  11467540 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b ae ae ae ae ae ae\n  11467560 ae ae ae ae ae ae ae ae ae ae ae ae ae ae ae ae\n  *\n  11777540 ae ae ae ae ae ae ae ae\n  11777550\n\n  # Unmount the filesystem and mount it again. This guarantees any file\n  # data in the page cache is dropped.\n  $ umount /dev/sdb\n  $ mount /dev/sdb /mnt\n\n  $ od -t x1 /mnt/foo\n  0000000 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b\n  *\n  11461300 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 00 00 00 00 00\n  11461320 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00\n  *\n  11470000 ae ae ae ae ae ae ae ae ae ae ae ae ae ae ae ae\n  *\n  11777540 ae ae ae ae ae ae ae ae\n  11777550\n\n  # The bytes in range 2515659 to 2519040 have a value of 0x00 and not a\n  # value of 0xae, data corruption happened due to the deduplication\n  # operation.\n\nSo fix this by rounding down, to the sector size, the length used for the\ndeduplication when the following conditions are met:\n\n  1) Source file's range ends at its i_size;\n  2) Source file's i_size is not aligned to the sector size;\n  3) Destination range does not cross the i_size of the destination file.\n\nFixes: e1d227a42ea2 (\"btrfs: Handle unaligned length in extent_same\")\nCC: stable@vger.kernel.org # 4.2+\nSigned-off-by: Filipe Manana <fdmanana@suse.com>\nSigned-off-by: David Sterba <dsterba@suse.com>","distinct":true,"url":"https://api.github.com/repos/woodsts/linux-stable/commits/de02b9f6bb65a6a1848f346f7a3617b7a9b930c0"},{"sha":"a5b7f4295eeae8b05ca91f6d145cd8773b08de9e","author":{"name":"Lu Fengqi","email":"6dbace5498dee639c6c1d42f6f8151420dfe2c5c@cn.fujitsu.com"},"message":"btrfs: fix qgroup_free wrong num_bytes in btrfs_subvolume_reserve_metadata\n\nAfter btrfs_qgroup_reserve_meta_prealloc(), num_bytes will be assigned\nagain by btrfs_calc_trans_metadata_size(). Once block_rsv fails, we\ncan't properly free the num_bytes of the previous qgroup_reserve. Use a\nseparate variable to store the num_bytes of the qgroup_reserve.\n\nDelete the comment for the qgroup_reserved that does not exist and add a\ncomment about use_global_rsv.\n\nFixes: c4c129db5da8 (\"btrfs: drop unused parameter qgroup_reserved\")\nCC: stable@vger.kernel.org # 4.18+\nSigned-off-by: Lu Fengqi <lufq.fnst@cn.fujitsu.com>\nReviewed-by: David Sterba <dsterba@suse.com>\nSigned-off-by: David Sterba <dsterba@suse.com>","distinct":true,"url":"https://api.github.com/repos/woodsts/linux-stable/commits/a5b7f4295eeae8b05ca91f6d145cd8773b08de9e"},{"sha":"801660b040d132f67fac6a95910ad307c5929b49","author":{"name":"Anand Jain","email":"81069a49b521acf79f562d472ec8c4e0d6a88433@oracle.com"},"message":"btrfs: btrfs_shrink_device should call commit transaction at the end\n\nTest case btrfs/164 reports use-after-free:\n\n[ 6712.084324] general protection fault: 0000 [#1] PREEMPT SMP\n..\n[ 6712.195423]  btrfs_update_commit_device_size+0x75/0xf0 [btrfs]\n[ 6712.201424]  btrfs_commit_transaction+0x57d/0xa90 [btrfs]\n[ 6712.206999]  btrfs_rm_device+0x627/0x850 [btrfs]\n[ 6712.211800]  btrfs_ioctl+0x2b03/0x3120 [btrfs]\n\nReason for this is that btrfs_shrink_device adds the resized device to\nthe fs_devices::resized_devices after it has called the last commit\ntransaction.\n\nSo the list fs_devices::resized_devices is not empty when\nbtrfs_shrink_device returns.  Now the parent function\nbtrfs_rm_device calls:\n\n        btrfs_close_bdev(device);\n        call_rcu(&device->rcu, free_device_rcu);\n\nand then does the transactio ncommit. It goes through the\nfs_devices::resized_devices in btrfs_update_commit_device_size and\nleads to use-after-free.\n\nFix this by making sure btrfs_shrink_device calls the last needed\nbtrfs_commit_transaction before the return. This is consistent with what\nthe grow counterpart does and this makes sure the on-disk state is\npersistent when the function returns.\n\nReported-by: Lu Fengqi <lufq.fnst@cn.fujitsu.com>\nTested-by: Lu Fengqi <lufq.fnst@cn.fujitsu.com>\nSigned-off-by: Anand Jain <anand.jain@oracle.com>\nReviewed-by: David Sterba <dsterba@suse.com>\n[ update changelog ]\nSigned-off-by: David Sterba <dsterba@suse.com>","distinct":true,"url":"https://api.github.com/repos/woodsts/linux-stable/commits/801660b040d132f67fac6a95910ad307c5929b49"},{"sha":"b9b8a41adeff5666b402996020b698504c927353","author":{"name":"Dan Carpenter","email":"ff341aa343d564f9e53e9dcb6996be8c04859a66@oracle.com"},"message":"btrfs: use after free in btrfs_quota_enable\n\nThe issue here is that btrfs_commit_transaction() frees \"trans\" on both\nthe error and the success path.  So the problem would be if\nbtrfs_commit_transaction() succeeds, and then qgroup_rescan_init()\nfails.  That means that \"ret\" is non-zero and \"trans\" is non-NULL and it\nleads to a use after free inside the btrfs_end_transaction() macro.\n\nFixes: 340f1aa27f36 (\"btrfs: qgroups: Move transaction management inside btrfs_quota_enable/disable\")\nSigned-off-by: Dan Carpenter <dan.carpenter@oracle.com>\nReviewed-by: Nikolay Borisov <nborisov@suse.com>\nReviewed-by: David Sterba <dsterba@suse.com>\nSigned-off-by: David Sterba <dsterba@suse.com>","distinct":true,"url":"https://api.github.com/repos/woodsts/linux-stable/commits/b9b8a41adeff5666b402996020b698504c927353"},{"sha":"b6fdfbff078975c53383fc146a2a54985eab6b6d","author":{"name":"Misono Tomohiro","email":"bc2c696bba6c0f8a788d4064c2d97b5d5542cf77@jp.fujitsu.com"},"message":"btrfs: Fix suspicious RCU usage warning in btrfs_debug_in_rcu\n\nCommit 672d599041c8 (\"btrfs: Use wrapper macro for rcu string to remove\nduplicate code\") replaces some open coded RCU string handling with macro.\n\nIt turns out that btrfs_debug_in_rcu() is used for the first time and\nthe macro lacks lock/unlock of RCU string for non-debug case (i.e. when\nthe message is not printed), leading to suspicious RCU usage warning\nwhen CONFIG_PROVE_RCU is on.\n\nFix this by adding a wrapper to call lock/unlock for the non-debug case\ntoo.\n\nFixes: 672d599041c8 (\"btrfs: Use wrapper macro for rcu string to remove duplicate code\")\nReported-by: David Howells <dhowells@redhat.com>\nTested-by: David Howells <dhowells@redhat.com>\nSigned-off-by: Misono Tomohiro <misono.tomohiro@jp.fujitsu.com>\nReviewed-by: David Sterba <dsterba@suse.com>\nSigned-off-by: David Sterba <dsterba@suse.com>","distinct":true,"url":"https://api.github.com/repos/woodsts/linux-stable/commits/b6fdfbff078975c53383fc146a2a54985eab6b6d"},{"sha":"d177c8b61d6b4ef360b1c2682e4d8e3bae01738b","author":{"name":"Icenowy Zheng","email":"cf9dc3e94649e480c789a6b538c4d95e82540aa4@aosc.io"},"message":"arm64: allwinner: dts: h6: fix Pine H64 MMC bus width\n\nCurrently the enabled MMC controllers on Pine H64 do not have bus-width\nset, which make them fall back to 1-bit mode and become quite slow.\n\nFix this by add the corresponding bus-width properties.\n\nFixes: ecbd611882a1 (\"arm64: allwinner: h6: enable MMC0/2 on Pine H64\")\nSigned-off-by: Icenowy Zheng <icenowy@aosc.io>\nSigned-off-by: Maxime Ripard <maxime.ripard@bootlin.com>","distinct":true,"url":"https://api.github.com/repos/woodsts/linux-stable/commits/d177c8b61d6b4ef360b1c2682e4d8e3bae01738b"},{"sha":"4051c323c59b535cfb7dc10b349544b4ad49c21e","author":{"name":"Alexey Brodkin","email":"1fa739873496c8c0c1b521f2061ee5fa4a0306e8@synopsys.com"},"message":"ARC: configs: cleanup\n\n - Remove CONFIG_DEFAULT_HOSTNAME from defconfigs\n\n   There's no reason to set the same hostname to all ARC boards\n   by default. It usually gets overwritten by init scripts anyways.\n\n - Remove disabled CONFIG_DEVKMEM from defconfigs\n\n   It is disabled by default\n\nSigned-off-by: Alexey Brodkin <abrodkin@synopsys.com>\nSigned-off-by: Vineet Gupta <vgupta@synopsys.com>","distinct":true,"url":"https://api.github.com/repos/woodsts/linux-stable/commits/4051c323c59b535cfb7dc10b349544b4ad49c21e"},{"sha":"5c0920897af59779546e9ea0e89c5db45c8aff33","author":{"name":"Alexey Brodkin","email":"1fa739873496c8c0c1b521f2061ee5fa4a0306e8@synopsys.com"},"message":"ARC: [plat-axs*/plat-hsdk]: Allow U-Boot to pass MAC-address to the kernel\n\nOtherwise kernel uses random MAC which is not very conveniet.\nWith that change in place use might set desired MAC in U-Boot\nwith \"setenv ethaddr 11:22:33:44:55:66\", save environment and\nthen from boot to boot the same MAC will be used by the kernel.\n\nOne other note for this to happen it's required to pass\nboard's .dtb in U-Boot's \"bootm\" command like that:\n------------------->8-----------------\nbootm 0x82000000 - 0x84000000\n------------------->8-----------------\n\nHere 0x82000000 is location of uImage while\n0x80000000 is location of either axs10x.dtb or hsdk.dtb\npreviously loaded from SD-card, USB storage or TFTP server.\n\nSigned-off-by: Alexey Brodkin <abrodkin@synopsys.com>\nCc: Rob Herring <robh+dt@kernel.org>\nCc: stable@vger.kernel.org # 4.14\nCc: devicetree@vger.kernel.org\nSigned-off-by: Vineet Gupta <vgupta@synopsys.com>","distinct":true,"url":"https://api.github.com/repos/woodsts/linux-stable/commits/5c0920897af59779546e9ea0e89c5db45c8aff33"},{"sha":"c83532fb0fe053d2e43e9387354cb1b52ba26427","author":{"name":"Alexey Brodkin","email":"1fa739873496c8c0c1b521f2061ee5fa4a0306e8@synopsys.com"},"message":"ARC: [plat-axs*]: Enable SWAP\n\nSWAP support on ARC was fixed earlier by\ncommit 6e3761145a9b (\"ARC: Fix CONFIG_SWAP\")\nso now we may safely enable it on platforms that\nhave external media like USB and SD-card.\n\nNote: it was already allowed for HSDK\n\nSigned-off-by: Alexey Brodkin <abrodkin@synopsys.com>\nCc: stable@vger.kernel.org # 6e3761145a9b: ARC: Fix CONFIG_SWAP\nSigned-off-by: Vineet Gupta <vgupta@synopsys.com>","distinct":true,"url":"https://api.github.com/repos/woodsts/linux-stable/commits/c83532fb0fe053d2e43e9387354cb1b52ba26427"},{"sha":"1e3bece2ded71eb85ac297a43002a942964e381d","author":{"name":"Eugeniy Paltsev","email":"ec089b543c2604b626d7ce60c03e4d074ed102c7@synopsys.com"},"message":"ARC: cleanup show_faulting_vma()\n\n - Remove unused variables\n - check return value of file_path\n\nSigned-off-by: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>\nSigned-off-by: Vineet Gupta <vgupta@synopsys.com>","distinct":true,"url":"https://api.github.com/repos/woodsts/linux-stable/commits/1e3bece2ded71eb85ac297a43002a942964e381d"},{"sha":"c27d0e9045bbbabffdde2bdba74e9971c4194ac4","author":{"name":"Vineet Gupta","email":"af669d95a4c0de051445d4cafdbb2c5c4a2838be@synopsys.com"},"message":"ARC: sort Kconfig\n\nSigned-off-by: Vineet Gupta <vgupta@synopsys.com>","distinct":true,"url":"https://api.github.com/repos/woodsts/linux-stable/commits/c27d0e9045bbbabffdde2bdba74e9971c4194ac4"},{"sha":"3fba68fa35a2cbda157c6f49f26eefccb2e10043","author":{"name":"Geert Uytterhoeven","email":"a1ff81395f7e6bf5b509fe9aab06bf3419493e1d@glider.be"},"message":"scsi: core: Update SCSI_MQ_DEFAULT help text to match default\n\nThe default was changed, but the help text was not updated.\n\nFix grammar (s/the option/this option/) while at it.\n\n[mkp: drop \"new\" as suggested by John Garry]\n\nFixes: d5038a13eca72fb2 (\"scsi: core: switch to scsi-mq by default\")\nSigned-off-by: Geert Uytterhoeven <geert+renesas@glider.be>\nReviewed-by: Ming Lei <ming.lei@redhat.com>\nSigned-off-by: Martin K. Petersen <martin.petersen@oracle.com>","distinct":true,"url":"https://api.github.com/repos/woodsts/linux-stable/commits/3fba68fa35a2cbda157c6f49f26eefccb2e10043"}]}
{"actor":{"display_login":"woodsts"}}