{"push_id":716415708,"size":16,"distinct_size":1,"ref":"refs/heads/topics/drivers/picoxcell-soc","head":"ea5f9565f36d4f840a0615c4ad75a78a034e7bbf","before":"ac6568daa6e50bb525c4cab06541bbfdb7159738","commits":[{"sha":"f992efbb0326ddf57c9d2f759c44a3339ab56a76","author":{"email":"271b10744f2b592adf8fde144d536c86b011b93c@gmail.com","name":"Pali Rohár"},"message":"dell-laptop: Update information about wireless control\n\nMake sure that all existing SMBIOS calls for wireless control are properly\ndocumented. This commit also add new documentation released by Dell.\n\nSigned-off-by: Pali Rohár <pali.rohar@gmail.com>\nSigned-off-by: Darren Hart <dvhart@linux.intel.com>","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/f992efbb0326ddf57c9d2f759c44a3339ab56a76"},{"sha":"2e19f93fecc502e68131e4433ef8d57ffa22bc3b","author":{"email":"271b10744f2b592adf8fde144d536c86b011b93c@gmail.com","name":"Pali Rohár"},"message":"dell-laptop: Show info about WiGig and UWB in debugfs\n\nThis commit show additional information about rfkill state in debugfs based\non newly released documentation by Dell.\n\nSigned-off-by: Pali Rohár <pali.rohar@gmail.com>\nSigned-off-by: Darren Hart <dvhart@linux.intel.com>","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/2e19f93fecc502e68131e4433ef8d57ffa22bc3b"},{"sha":"b8830a4e71b15d0364ac8e6c55301eea73f211da","author":{"email":"271b10744f2b592adf8fde144d536c86b011b93c@gmail.com","name":"Pali Rohár"},"message":"dell-laptop: Fix allocating & freeing SMI buffer page\n\nThis commit fix kernel crash when probing for rfkill devices in dell-laptop\ndriver failed. Function free_page() was incorrectly used on struct page *\ninstead of virtual address of SMI buffer.\n\nThis commit also simplify allocating page for SMI buffer by using\n__get_free_page() function instead of sequential call of functions\nalloc_page() and page_address().\n\nSigned-off-by: Pali Rohár <pali.rohar@gmail.com>\nAcked-by: Michal Hocko <mhocko@suse.cz>\nCc: stable@vger.kernel.org\nSigned-off-by: Darren Hart <dvhart@linux.intel.com>","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/b8830a4e71b15d0364ac8e6c55301eea73f211da"},{"sha":"0d44b410a01a75daff60ce4cb78313135cdb3649","author":{"email":"da4b4ed1d87736710c484a0ca84b2abc9f4ef095@users.sourceforge.net","name":"Markus Elfring"},"message":"tc1100-wmi: Delete an unnecessary check before the function call \"kfree\"\n\nThe kfree() function tests whether its argument is NULL and then\nreturns immediately. Thus the test around the call is not needed.\n\nThis issue was detected by using the Coccinelle software.\n\nSigned-off-by: Markus Elfring <elfring@users.sourceforge.net>\nSigned-off-by: Darren Hart <dvhart@linux.intel.com>","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/0d44b410a01a75daff60ce4cb78313135cdb3649"},{"sha":"0a8b83530b6f67b9a50bd7937d57a5deea187b5b","author":{"email":"a8f71c12270d4aa03666e926cbad245d71c25649@intel.com","name":"qipeng.zha"},"message":"intel_pmc_ipc: Add Intel Apollo Lake PMC IPC driver\n\nThis driver provides support for PMC control on Apollo Lake platforms.\nThe PMC is an ARC processor which defines some IPC commands for\ncommunication with other entities in the CPU.\n\nSigned-off-by: qipeng.zha <qipeng.zha@intel.com>\n[fengguang.wu@intel.com: Fix Sparse and Cocinelle warnings]\nSigned-off-by: Fengguang Wu <fengguang.wu@intel.com>\nSigned-off-by: Darren Hart <dvhart@linux.intel.com>","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/0a8b83530b6f67b9a50bd7937d57a5deea187b5b"},{"sha":"0f0ff9a9f3fa2ec6f427603fd521d5f3a0b076d1","author":{"email":"4ed386e0495d3e109932df055831d9ec2f824927@mit.edu","name":"Theodore Ts'o"},"message":"ext4: fix fencepost error in lazytime optimization\n\nCommit 8f4d8558391: \"ext4: fix lazytime optimization\" was not a\ncomplete fix.  In the case where the inode number is a multiple of 16,\nand we could still end up updating an inode with dirty timestamps\nwritten to the wrong inode on disk.  Oops.\n\nThis can be easily reproduced by using generic/005 with a file system\nwith metadata_csum and lazytime enabled.\n\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>\nCc: stable@vger.kernel.org","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/0f0ff9a9f3fa2ec6f427603fd521d5f3a0b076d1"},{"sha":"bd7ade3cd9b0850264306f5c2b79024a417b6396","author":{"email":"c65a0fb7e74ffd2c9fc3a0f9aacb0f6a24b0a68b@kyup.com","name":"Nikolay Borisov"},"message":"bufferhead: Add _gfp version for sb_getblk()\n\nsb_getblk() is used during ext4 (and possibly other FSes) writeback\npaths. Sometimes such path require allocating memory and guaranteeing\nthat such allocation won't block. Currently, however, there is no way\nto provide user flags for sb_getblk which could lead to deadlocks.\n\nThis patch implements a sb_getblk_gfp with the only difference it can\naccept user-provided GFP flags.\n\nSigned-off-by: Nikolay Borisov <kernel@kyup.com>\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>\nCc: stable@vger.kernel.org","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/bd7ade3cd9b0850264306f5c2b79024a417b6396"},{"sha":"c45653c341f5c8a0ce19c8f0ad4678640849cb86","author":{"email":"c65a0fb7e74ffd2c9fc3a0f9aacb0f6a24b0a68b@kyup.com","name":"Nikolay Borisov"},"message":"ext4: avoid deadlocks in the writeback path by using sb_getblk_gfp\n\nSwitch ext4 to using sb_getblk_gfp with GFP_NOFS added to fix possible\ndeadlocks in the page writeback path.\n\nSigned-off-by: Nikolay Borisov <kernel@kyup.com>\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>\nCc: stable@vger.kernel.org","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/c45653c341f5c8a0ce19c8f0ad4678640849cb86"},{"sha":"9705acd63b125dee8b15c705216d7186daea4625","author":{"email":"6c9141d0e2318b390a8a6bf8ecd9f819d16f05b4@redhat.com","name":"Lukas Czerner"},"message":"ext4: fix reservation release on invalidatepage for delalloc fs\n\nOn delalloc enabled file system on invalidatepage operation\nin ext4_da_page_release_reservation() we want to clear the delayed\nbuffer and remove the extent covering the delayed buffer from the extent\nstatus tree.\n\nHowever currently there is a bug where on the systems with page size >\nblock size we will always remove extents from the start of the page\nregardless where the actual delayed buffers are positioned in the page.\nThis leads to the errors like this:\n\nEXT4-fs warning (device loop0): ext4_da_release_space:1225:\next4_da_release_space: ino 13, to_free 1 with only 0 reserved data\nblocks\n\nThis however can cause data loss on writeback time if the file system is\nin ENOSPC condition because we're releasing reservation for someones\nelse delayed buffer.\n\nFix this by only removing extents that corresponds to the part of the\npage we want to invalidate.\n\nThis problem is reproducible by the following fio receipt (however I was\nonly able to reproduce it with fio-2.1 or older.\n\n[global]\nbs=8k\niodepth=1024\niodepth_batch=60\nrandrepeat=1\nsize=1m\ndirectory=/mnt/test\nnumjobs=20\n[job1]\nioengine=sync\nbs=1k\ndirect=1\nrw=randread\nfilename=file1:file2\n[job2]\nioengine=libaio\nrw=randwrite\ndirect=1\nfilename=file1:file2\n[job3]\nbs=1k\nioengine=posixaio\nrw=randwrite\ndirect=1\nfilename=file1:file2\n[job5]\nbs=1k\nioengine=sync\nrw=randread\nfilename=file1:file2\n[job7]\nioengine=libaio\nrw=randwrite\nfilename=file1:file2\n[job8]\nioengine=posixaio\nrw=randwrite\nfilename=file1:file2\n[job10]\nioengine=mmap\nrw=randwrite\nbs=1k\nfilename=file1:file2\n[job11]\nioengine=mmap\nrw=randwrite\ndirect=1\nfilename=file1:file2\n\nSigned-off-by: Lukas Czerner <lczerner@redhat.com>\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>\nReviewed-by: Jan Kara <jack@suse.cz>\nCc: stable@vger.kernel.org","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/9705acd63b125dee8b15c705216d7186daea4625"},{"sha":"d6f123a9297496ad0b6335fe881504c4b5b2a5e5","author":{"email":"45077a34947a1ae82e6576c6adeb38fe04811905@gmail.com","name":"Eryu Guan"},"message":"ext4: be more strict when migrating to non-extent based file\n\nCurrently the check in ext4_ind_migrate() is not enough before doing the\nreal conversion:\n\na) delayed allocated extents could bypass the check on eh->eh_entries\n   and eh->eh_depth\n\nThis can be demonstrated by this script\n\n  xfs_io -fc \"pwrite 0 4k\" -c \"pwrite 8k 4k\" /mnt/ext4/testfile\n  chattr -e /mnt/ext4/testfile\n\nwhere testfile has two extents but still be converted to non-extent\nbased file format.\n\nb) only extent length is checked but not the offset, which would result\n   in data lose (delalloc) or fs corruption (nodelalloc), because\n   non-extent based file only supports at most (12 + 2^10 + 2^20 + 2^30)\n   blocks\n\nThis can be demostrated by\n\n  xfs_io -fc \"pwrite 5T 4k\" /mnt/ext4/testfile\n  chattr -e /mnt/ext4/testfile\n  sync\n\nIf delalloc is enabled, dmesg prints\n  EXT4-fs warning (device dm-4): ext4_block_to_path:105: block 1342177280 > max in inode 53\n  EXT4-fs (dm-4): Delayed block allocation failed for inode 53 at logical offset 1342177280 with max blocks 1 with error 5\n  EXT4-fs (dm-4): This should not happen!! Data will be lost\n\nIf delalloc is disabled, e2fsck -nf shows corruption\n  Inode 53, i_size is 5497558142976, should be 4096.  Fix? no\n\nFix the two issues by\n\na) forcing all delayed allocation blocks to be allocated before checking\n   eh->eh_depth and eh->eh_entries\nb) limiting the last logical block of the extent is within direct map\n\nSigned-off-by: Eryu Guan <guaneryu@gmail.com>\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>\nCc: stable@vger.kernel.org","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/d6f123a9297496ad0b6335fe881504c4b5b2a5e5"},{"sha":"8974fec7d72e3e02752fe0f27b4c3719c78d9a15","author":{"email":"45077a34947a1ae82e6576c6adeb38fe04811905@gmail.com","name":"Eryu Guan"},"message":"ext4: correctly migrate a file with a hole at the beginning\n\nCurrently ext4_ind_migrate() doesn't correctly handle a file which\ncontains a hole at the beginning of the file.  This caused the migration\nto be done incorrectly, and then if there is a subsequent following\ndelayed allocation write to the \"hole\", this would reclaim the same data\nblocks again and results in fs corruption.\n\n  # assmuing 4k block size ext4, with delalloc enabled\n  # skip the first block and write to the second block\n  xfs_io -fc \"pwrite 4k 4k\" -c \"fsync\" /mnt/ext4/testfile\n\n  # converting to indirect-mapped file, which would move the data blocks\n  # to the beginning of the file, but extent status cache still marks\n  # that region as a hole\n  chattr -e /mnt/ext4/testfile\n\n  # delayed allocation writes to the \"hole\", reclaim the same data block\n  # again, results in i_blocks corruption\n  xfs_io -c \"pwrite 0 4k\" /mnt/ext4/testfile\n  umount /mnt/ext4\n  e2fsck -nf /dev/sda6\n  ...\n  Inode 53, i_blocks is 16, should be 8.  Fix? no\n  ...\n\nSigned-off-by: Eryu Guan <guaneryu@gmail.com>\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>\nCc: stable@vger.kernel.org","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/8974fec7d72e3e02752fe0f27b4c3719c78d9a15"},{"sha":"7444a072c387a93ebee7066e8aee776954ab0e41","author":{"email":"829500b200af6c2a0eca4dfd5c388e6b8fbe8dc6@suse.cz","name":"Michal Hocko"},"message":"ext4: replace open coded nofail allocation in ext4_free_blocks()\n\next4_free_blocks is looping around the allocation request and mimics\n__GFP_NOFAIL behavior without any allocation fallback strategy. Let's\nremove the open coded loop and replace it with __GFP_NOFAIL. Without the\nflag the allocator has no way to find out never-fail requirement and\ncannot help in any way.\n\nSigned-off-by: Michal Hocko <mhocko@suse.cz>\nSigned-off-by: Theodore Ts'o <tytso@mit.edu>\nCc: stable@vger.kernel.org","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/7444a072c387a93ebee7066e8aee776954ab0e41"},{"sha":"a585d2b738bfa26326b3f1f40f0f1eda0c067ccf","author":{"email":"69652caca27c8b940640ad396ab71f93cacec34f@linux-foundation.org","name":"Linus Torvalds"},"message":"Merge tag 'platform-drivers-x86-v4.2-2' of git://git.infradead.org/users/dvhart/linux-platform-drivers-x86\n\nPull late x86 platform driver updates from Darren Hart:\n \"The following came in a bit later and I wanted them to bake in next a\n  few more days before submitting, thus the second pull.\n\n  A new intel_pmc_ipc driver, a symmetrical allocation and free fix in\n  dell-laptop, a couple minor fixes, and some updated documentation in\n  the dell-laptop comments.\n\n  intel_pmc_ipc:\n   - Add Intel Apollo Lake PMC IPC driver\n\n  tc1100-wmi:\n   - Delete an unnecessary check before the function call \"kfree\"\n\n  dell-laptop:\n   - Fix allocating & freeing SMI buffer page\n   - Show info about WiGig and UWB in debugfs\n   - Update information about wireless control\"\n\n* tag 'platform-drivers-x86-v4.2-2' of git://git.infradead.org/users/dvhart/linux-platform-drivers-x86:\n  intel_pmc_ipc: Add Intel Apollo Lake PMC IPC driver\n  tc1100-wmi: Delete an unnecessary check before the function call \"kfree\"\n  dell-laptop: Fix allocating & freeing SMI buffer page\n  dell-laptop: Show info about WiGig and UWB in debugfs\n  dell-laptop: Update information about wireless control","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/a585d2b738bfa26326b3f1f40f0f1eda0c067ccf"},{"sha":"d770e558e21961ad6cfdf0ff7df0eb5d7d4f0754","author":{"email":"69652caca27c8b940640ad396ab71f93cacec34f@linux-foundation.org","name":"Linus Torvalds"},"message":"Linux 4.2-rc1","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/d770e558e21961ad6cfdf0ff7df0eb5d7d4f0754"},{"sha":"1c4c7159ed2468f3ac4ce5a7f08d79663d381a93","author":{"email":"69652caca27c8b940640ad396ab71f93cacec34f@linux-foundation.org","name":"Linus Torvalds"},"message":"Merge tag 'ext4_for_linus_stable' of git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4\n\nPull ext4 bugfixes from Ted Ts'o:\n \"Bug fixes (all for stable kernels) for ext4:\n\n   - address corner cases for indirect blocks->extent migration\n\n   - fix reserved block accounting invalidate_page when\n     page_size != block_size (i.e., ppc or 1k block size file systems)\n\n   - fix deadlocks when a memcg is under heavy memory pressure\n\n   - fix fencepost error in lazytime optimization\"\n\n* tag 'ext4_for_linus_stable' of git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4:\n  ext4: replace open coded nofail allocation in ext4_free_blocks()\n  ext4: correctly migrate a file with a hole at the beginning\n  ext4: be more strict when migrating to non-extent based file\n  ext4: fix reservation release on invalidatepage for delalloc fs\n  ext4: avoid deadlocks in the writeback path by using sb_getblk_gfp\n  bufferhead: Add _gfp version for sb_getblk()\n  ext4: fix fencepost error in lazytime optimization","distinct":false,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/1c4c7159ed2468f3ac4ce5a7f08d79663d381a93"},{"sha":"ea5f9565f36d4f840a0615c4ad75a78a034e7bbf","author":{"email":"17b9e1c64588c7fa6419b4d29dc1f4426279ba01@smart-africa.com","name":"Michael van der Westhuizen"},"message":"SoC drivers for picoXcell","distinct":true,"url":"https://api.github.com/repos/r1mikey/linux-picoxcell/commits/ea5f9565f36d4f840a0615c4ad75a78a034e7bbf"}]}