{"push_id":2520656065,"size":91,"distinct_size":0,"ref":"refs/heads/master","head":"0644f186fc9d77bb5bd198369e59fb28927a3692","before":"26ed24e429d89e045e5eb2d2b75215244347b7f2","commits":[{"sha":"1dc3039bc87ae7d19a990c3ee71cfd8a9068f428","author":{"name":"Alan Jenkins","email":"80a2edbb6a10db4ca229372563196b5c5e6cb878@gmail.com"},"message":"block: do not use interruptible wait anywhere\n\nWhen blk_queue_enter() waits for a queue to unfreeze, or unset the\nPREEMPT_ONLY flag, do not allow it to be interrupted by a signal.\n\nThe PREEMPT_ONLY flag was introduced later in commit 3a0a529971ec\n(\"block, scsi: Make SCSI quiesce and resume work reliably\").  Note the SCSI\ndevice is resumed asynchronously, i.e. after un-freezing userspace tasks.\n\nSo that commit exposed the bug as a regression in v4.15.  A mysterious\nSIGBUS (or -EIO) sometimes happened during the time the device was being\nresumed.  Most frequently, there was no kernel log message, and we saw Xorg\nor Xwayland killed by SIGBUS.[1]\n\n[1] E.g. https://bugzilla.redhat.com/show_bug.cgi?id=1553979\n\nWithout this fix, I get an IO error in this test:\n\n# dd if=/dev/sda of=/dev/null iflag=direct & \\\n  while killall -SIGUSR1 dd; do sleep 0.1; done & \\\n  echo mem > /sys/power/state ; \\\n  sleep 5; killall dd  # stop after 5 seconds\n\nThe interruptible wait was added to blk_queue_enter in\ncommit 3ef28e83ab15 (\"block: generic request_queue reference counting\").\nBefore then, the interruptible wait was only in blk-mq, but I don't think\nit could ever have been correct.\n\nReviewed-by: Bart Van Assche <bart.vanassche@wdc.com>\nCc: stable@vger.kernel.org\nSigned-off-by: Alan Jenkins <alan.christopher.jenkins@gmail.com>\nSigned-off-by: Jens Axboe <axboe@kernel.dk>","distinct":false,"url":"https://api.github.com/repos/masahir0y/linux-yamada/commits/1dc3039bc87ae7d19a990c3ee71cfd8a9068f428"},{"sha":"1894e916546df0efec9890a5c9954f4ad281494c","author":{"name":"Jens Axboe","email":"cd8c6775e60d6f67a6984377324e5290df3d5358@kernel.dk"},"message":"loop: remove cmd->rq member\n\nWe can always get at the request from the payload, no need to store\na pointer to it.\n\nReviewed-by: Ming Lei <ming.lei@redhat.com>\nSigned-off-by: Jens Axboe <axboe@kernel.dk>","distinct":false,"url":"https://api.github.com/repos/masahir0y/linux-yamada/commits/1894e916546df0efec9890a5c9954f4ad281494c"},{"sha":"f9de14bc7e7aac77fd44bb2f62206eb9e494f0d2","author":{"name":"Jens Axboe","email":"cd8c6775e60d6f67a6984377324e5290df3d5358@kernel.dk"},"message":"loop: handle short DIO reads\n\nWe ran into an issue with loop and btrfs, where btrfs would complain about\nchecksum errors. It turns out that is because we don't handle short reads\nat all, we just zero fill the remainder. Worse than that, we don't handle\nthe filling properly, which results in loop trying to advance a single\nbio by much more than its size, since it doesn't take chaining into\naccount.\n\nHandle short reads appropriately, by simply retrying at the new correct\noffset. End the remainder of the request with EIO, if we get a 0 read.\n\nFixes: bc07c10a3603 (\"block: loop: support DIO & AIO\")\nReviewed-by: Ming Lei <ming.lei@redhat.com>\nSigned-off-by: Jens Axboe <axboe@kernel.dk>","distinct":false,"url":"https://api.github.com/repos/masahir0y/linux-yamada/commits/f9de14bc7e7aac77fd44bb2f62206eb9e494f0d2"},{"sha":"660661afcd40ed7f515ef3369721ed58e80c0fc5","author":{"name":"Victor Gu","email":"c704438b5004f6787371acbf89b0bfea8806f455@marvell.com"},"message":"PCI: aardvark: Fix logic in advk_pcie_{rd,wr}_conf()\n\nThe PCI configuration space read/write functions were special casing\nthe situation where PCI_SLOT(devfn) != 0, and returned\nPCIBIOS_DEVICE_NOT_FOUND in this case.\n\nHowever, while this is what is intended for the root bus, it is not\nintended for the child busses, as it prevents discovering devices with\nPCI_SLOT(x) != 0. Therefore, we return PCIBIOS_DEVICE_NOT_FOUND only\nif we're on the root bus.\n\nFixes: 8c39d710363c1 (\"PCI: aardvark: Add Aardvark PCI host controller driver\")\nCc: <stable@vger.kernel.org>\nSigned-off-by: Victor Gu <xigu@marvell.com>\nReviewed-by: Wilson Ding <dingwei@marvell.com>\nReviewed-by: Nadav Haklai <nadavh@marvell.com>\n[Thomas: tweak commit log.]\nSigned-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>\nSigned-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>","distinct":false,"url":"https://api.github.com/repos/masahir0y/linux-yamada/commits/660661afcd40ed7f515ef3369721ed58e80c0fc5"},{"sha":"4fa3999ee672c54a5498ce98e20fe3fdf9c1cbb4","author":{"name":"Victor Gu","email":"c704438b5004f6787371acbf89b0bfea8806f455@marvell.com"},"message":"PCI: aardvark: Set PIO_ADDR_LS correctly in advk_pcie_rd_conf()\n\nWhen setting the PIO_ADDR_LS register during a configuration read, we\nwere properly passing the device number, function number and register\nnumber, but not the bus number, causing issues when reading the\nconfiguration of PCIe devices.\n\nFixes: 8c39d710363c1 (\"PCI: aardvark: Add Aardvark PCI host controller driver\")\nCc: <stable@vger.kernel.org>\nSigned-off-by: Victor Gu <xigu@marvell.com>\nReviewed-by: Wilson Ding <dingwei@marvell.com>\nReviewed-by: Nadav Haklai <nadavh@marvell.com>\n[Thomas: tweak commit log.]\nSigned-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>\nSigned-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>","distinct":false,"url":"https://api.github.com/repos/masahir0y/linux-yamada/commits/4fa3999ee672c54a5498ce98e20fe3fdf9c1cbb4"},{"sha":"3430f924a62905891c8fa9a3b97ea52007795bc3","author":{"name":"Victor Gu","email":"c704438b5004f6787371acbf89b0bfea8806f455@marvell.com"},"message":"PCI: aardvark: Use ISR1 instead of ISR0 interrupt in legacy irq mode\n\nThe Aardvark has two interrupts sets:\n\n - first set is bit[23:16] of PCIe ISR 0 register(RD0074840h)\n\n - second set is bit[11:8] of PCIe ISR 1 register(RD0074848h)\n\nOnly one set should be used, while another set should be masked.\n\nThe second set, ISR1, is more advanced, the Legacy INT_X status bit is\nasserted once Assert_INTX message is received, and de-asserted after\nDeassert_INTX message is received which matches what the driver is\ncurrently doing in the ->irq_mask() and ->irq_unmask() functions.\n\nThe ISR0 requires additional work to deassert the interrupt, which the\ndriver does not currently implement, therefore it needs fixing.\n\nUpdate the driver to use ISR1 register set, fixing current\nimplementation.\n\nFixes: 8c39d710363c1 (\"PCI: aardvark: Add Aardvark PCI host controller driver\")\nLink: https://bugzilla.kernel.org/show_bug.cgi?id=196339\nSigned-off-by: Victor Gu <xigu@marvell.com>\n[Thomas: tweak commit log.]\nSigned-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>\n[lorenzo.pieralisi@arm.com: updated the commit log]\nSigned-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>\nReviewed-by: Evan Wang <xswang@marvell.com>\nReviewed-by: Nadav Haklai <nadavh@marvell.com>\nCc: <stable@vger.kernel.org>","distinct":false,"url":"https://api.github.com/repos/masahir0y/linux-yamada/commits/3430f924a62905891c8fa9a3b97ea52007795bc3"},{"sha":"fc31c4e347c9dad50544d01d5ee98b22c7df88bb","author":{"name":"Evan Wang","email":"a5dd7e6df0cf510cb80348f8e55d69f128a44339@marvell.com"},"message":"PCI: aardvark: Fix PCIe Max Read Request Size setting\n\nThere is an obvious typo issue in the definition of the PCIe maximum\nread request size: a bit shift is directly used as a value, while it\nshould be used to shift the correct value.\n\nFixes: 8c39d710363c1 (\"PCI: aardvark: Add Aardvark PCI host controller driver\")\nCc: <stable@vger.kernel.org>\nSigned-off-by: Evan Wang <xswang@marvell.com>\nReviewed-by: Victor Gu <xigu@marvell.com>\nReviewed-by: Nadav Haklai <nadavh@marvell.com>\n[Thomas: tweak commit log.]\nSigned-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>\nSigned-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>","distinct":false,"url":"https://api.github.com/repos/masahir0y/linux-yamada/commits/fc31c4e347c9dad50544d01d5ee98b22c7df88bb"},{"sha":"b64576cbf36afa5fabf3b31f62a1994c429ef855","author":{"name":"Finn Thain","email":"94052abb058aed443995dc4f8d236e022112765d@telegraphics.com.au"},"message":"m68k/mac: Don't remap SWIM MMIO region\n\nFor reasons I don't understand, calling ioremap() then iounmap() on\nthe SWIM MMIO region causes a hang on 68030 (but not on 68040).\n\n~# modprobe swim_mod\nSWIM floppy driver Version 0.2 (2008-10-30)\nSWIM device not found !\nwatchdog: BUG: soft lockup - CPU#0 stuck for 23s! [modprobe:285]\nModules linked in: swim_mod(+)\nFormat 00  Vector: 0064  PC: 000075aa  Status: 2000    Not tainted\nORIG_D0: ffffffff  D0: d00c0000  A2: 007c2370  A1: 003f810c\nA0: 00040000  D5: d0096800  D4: d0097e00\nD3: 00000001  D2: 00000003  D1: 00000000\nNon-Maskable Interrupt\nModules linked in: swim_mod(+)\nPC: [<000075ba>] __iounmap+0x24/0x10e\nSR: 2000  SP: 007abc48  a2: 007c2370\nd0: d00c0000    d1: 000001a0    d2: 00000019    d3: 00000001\nd4: d0097e00    d5: d0096800    a0: 00040000    a1: 003f810c\nProcess modprobe (pid: 285, task=007c2370)\nFrame format=0\nStack from 007abc7c:\n        ffffffed 00000000 006a4060 004712e0 007abca0 000076ea d0080000 00080000\n        010bb4b8 007abcd8 010ba542 d0096000 00000000 00000000 00000001 010bb59c\n        00000000 007abf30 010bb4b8 0047760a 0047763c 00477612 00616540 007abcec\n        0020a91a 00477600 0047760a 010bb4cc 007abd18 002092f2 0047760a 00333b06\n        007abd5c 00000000 0047760a 010bb4cc 00404f90 004776b8 00000001 007abd38\n        00209446 010bb4cc 0047760a 010bb4cc 0020938e 0031f8be 00616540 007abd64\nCall Trace: [<000076ea>] iounmap+0x46/0x5a\n [<00080000>] shrink_page_list+0x7f6/0xe06\n [<010ba542>] swim_probe+0xe4/0x496 [swim_mod]\n [<0020a91a>] platform_drv_probe+0x20/0x5e\n [<002092f2>] driver_probe_device+0x21c/0x2b8\n [<00333b06>] mutex_lock+0x0/0x2e\n [<00209446>] __driver_attach+0xb8/0xce\n [<0020938e>] __driver_attach+0x0/0xce\n [<0031f8be>] klist_next+0x0/0xa0\n [<00207562>] bus_for_each_dev+0x74/0xba\n [<000344c0>] blocking_notifier_call_chain+0x0/0x20\n [<00333b06>] mutex_lock+0x0/0x2e\n [<00208e44>] driver_attach+0x1a/0x1e\n [<0020938e>] __driver_attach+0x0/0xce\n [<00207e26>] bus_add_driver+0x188/0x234\n [<000344c0>] blocking_notifier_call_chain+0x0/0x20\n [<00209894>] driver_register+0x58/0x104\n [<000344c0>] blocking_notifier_call_chain+0x0/0x20\n [<010bd000>] swim_init+0x0/0x2c [swim_mod]\n [<0020a7be>] __platform_driver_register+0x38/0x3c\n [<010bd028>] swim_init+0x28/0x2c [swim_mod]\n [<000020dc>] do_one_initcall+0x38/0x196\n [<000344c0>] blocking_notifier_call_chain+0x0/0x20\n [<003331cc>] mutex_unlock+0x0/0x3e\n [<00333b06>] mutex_lock+0x0/0x2e\n [<003331cc>] mutex_unlock+0x0/0x3e\n [<00333b06>] mutex_lock+0x0/0x2e\n [<003331cc>] mutex_unlock+0x0/0x3e\n [<00333b06>] mutex_lock+0x0/0x2e\n [<003331cc>] mutex_unlock+0x0/0x3e\n [<00333b06>] mutex_lock+0x0/0x2e\n [<00075008>] __free_pages+0x0/0x38\n [<000045c0>] mangle_kernel_stack+0x30/0xda\n [<000344c0>] blocking_notifier_call_chain+0x0/0x20\n [<003331cc>] mutex_unlock+0x0/0x3e\n [<00333b06>] mutex_lock+0x0/0x2e\n [<0005ced4>] do_init_module+0x42/0x266\n [<010bd000>] swim_init+0x0/0x2c [swim_mod]\n [<000344c0>] blocking_notifier_call_chain+0x0/0x20\n [<0005eda0>] load_module+0x1a30/0x1e70\n [<0000465d>] mangle_kernel_stack+0xcd/0xda\n [<00331c64>] __generic_copy_from_user+0x0/0x46\n [<0033256e>] _cond_resched+0x0/0x32\n [<00331b9c>] memset+0x0/0x98\n [<0033256e>] _cond_resched+0x0/0x32\n [<0005f25c>] SyS_init_module+0x7c/0x112\n [<00002000>] _start+0x0/0x8\n [<00002000>] _start+0x0/0x8\n [<00331c82>] __generic_copy_from_user+0x1e/0x46\n [<0005f2b2>] SyS_init_module+0xd2/0x112\n [<0000465d>] mangle_kernel_stack+0xcd/0xda\n [<00002b40>] syscall+0x8/0xc\n [<0000465d>] mangle_kernel_stack+0xcd/0xda\n [<0008c00c>] pcpu_balance_workfn+0xb2/0x40e\nCode: 2200 7419 e4a9 e589 2841 d9fc 0000 1000 <2414> 7203 c282 7602 b681 6600 0096 0242 fe00 0482 0000 0000 e9c0 11c3 ed89 2642\n\nThere's no need to call ioremap() for the SWIM address range, as it lies\nwithin the usual IO device region at 0x5000 0000, which has already been\nmapped by head.S.\n\nRemove the redundant ioremap() and iounmap() calls to fix the hang.\n\nCc: Laurent Vivier <lvivier@redhat.com>\nCc: stable@vger.kernel.org # v4.14+\nTested-by: Stan Johnson <userm57@yahoo.com>\nSigned-off-by: Finn Thain <fthain@telegraphics.com.au>\nAcked-by: Laurent Vivier <lvivier@redhat.com>\nSigned-off-by: Jens Axboe <axboe@kernel.dk>","distinct":false,"url":"https://api.github.com/repos/masahir0y/linux-yamada/commits/b64576cbf36afa5fabf3b31f62a1994c429ef855"},{"sha":"7ae6a2b6cc058005ee3d0d2b9ce27688e51afa4b","author":{"name":"Finn Thain","email":"94052abb058aed443995dc4f8d236e022112765d@telegraphics.com.au"},"message":"block/swim: Fix array bounds check\n\nIn the floppy_find() function in swim.c is a call to\nget_disk(swd->unit[drive].disk). The actual parameter to this call\ncan be a NULL pointer when drive == swd->floppy_count. This causes\nan oops in get_disk().\n\nData read fault at 0x00000198 in Super Data (pc=0x1be5b6)\nBAD KERNEL BUSERR\nOops: 00000000\nModules linked in: swim_mod ipv6 mac8390\nPC: [<001be5b6>] get_disk+0xc/0x76\nSR: 2004  SP: 9a078bc1  a2: 0213ed90\nd0: 00000000    d1: 00000000    d2: 00000000    d3: 000000ff\nd4: 00000002    d5: 02983590    a0: 02332e00    a1: 022dfd64\nProcess dd (pid: 285, task=020ab25b)\nFrame format=B ssw=074d isc=4a88 isb=6732 daddr=00000198 dobuf=00000000\nbaddr=001be5bc dibuf=bfffffff ver=f\nStack from 022dfca4:\n        00000000 0203fc00 0213ed90 022dfcc0 02982936 00000000 00200000 022dfd08\n        0020f85a 00200000 022dfd64 02332e00 004040fc 00000014 001be77e 022dfd64\n        00334e4a 001be3f8 0800001d 022dfd64 01c04b60 01c04b70 022aba80 029828f8\n        02332e00 022dfd2c 001be7ac 0203fc00 00200000 022dfd64 02103a00 01c04b60\n        01c04b60 0200e400 022dfd68 000e191a 00200000 022dfd64 02103a00 0800001d\n        00000000 00000003 000b89de 00500000 02103a00 01c04b60 02103a08 01c04c2e\nCall Trace: [<02982936>] floppy_find+0x3e/0x4a [swim_mod]\n [<00200000>] uart_remove_one_port+0x1a2/0x260\n [<0020f85a>] kobj_lookup+0xde/0x132\n [<00200000>] uart_remove_one_port+0x1a2/0x260\n [<001be77e>] get_gendisk+0x0/0x130\n [<00334e4a>] mutex_lock+0x0/0x2e\n [<001be3f8>] disk_block_events+0x0/0x6c\n [<029828f8>] floppy_find+0x0/0x4a [swim_mod]\n [<001be7ac>] get_gendisk+0x2e/0x130\n [<00200000>] uart_remove_one_port+0x1a2/0x260\n [<000e191a>] __blkdev_get+0x32/0x45a\n [<00200000>] uart_remove_one_port+0x1a2/0x260\n [<000b89de>] complete_walk+0x0/0x8a\n [<000e1e22>] blkdev_get+0xe0/0x29a\n [<000e1fdc>] blkdev_open+0x0/0xb0\n [<000b89de>] complete_walk+0x0/0x8a\n [<000e1fdc>] blkdev_open+0x0/0xb0\n [<000e01cc>] bd_acquire+0x74/0x8a\n [<000e205c>] blkdev_open+0x80/0xb0\n [<000e1fdc>] blkdev_open+0x0/0xb0\n [<000abf24>] do_dentry_open+0x1a4/0x322\n [<00020000>] __do_proc_douintvec+0x22/0x27e\n [<000b89de>] complete_walk+0x0/0x8a\n [<000baa62>] link_path_walk+0x0/0x48e\n [<000ba3f8>] inode_permission+0x20/0x54\n [<000ac0e4>] vfs_open+0x42/0x78\n [<000bc372>] path_openat+0x2b2/0xeaa\n [<000bc0c0>] path_openat+0x0/0xeaa\n [<0004463e>] __irq_wake_thread+0x0/0x4e\n [<0003a45a>] task_tick_fair+0x18/0xc8\n [<000bd00a>] do_filp_open+0xa0/0xea\n [<000abae0>] do_sys_open+0x11a/0x1ee\n [<00020000>] __do_proc_douintvec+0x22/0x27e\n [<000abbf4>] SyS_open+0x1e/0x22\n [<00020000>] __do_proc_douintvec+0x22/0x27e\n [<00002b40>] syscall+0x8/0xc\n [<00020000>] __do_proc_douintvec+0x22/0x27e\n [<0000c00b>] dyadic+0x1/0x28\nCode: 4e5e 4e75 4e56 fffc 2f0b 2f02 266e 0008 <206b> 0198 4a88 6732 2428 002c 661e 486b 0058 4eb9 0032 0b96 588f 4a88 672c 2008\nDisabling lock debugging due to kernel taint\n\nFix the array index bounds check to avoid this.\n\nCc: Laurent Vivier <lvivier@redhat.com>\nCc: Jens Axboe <axboe@kernel.dk>\nCc: stable@vger.kernel.org # v4.14+\nFixes: 8852ecd97488 (\"[PATCH] m68k: mac - Add SWIM floppy support\")\nTested-by: Stan Johnson <userm57@yahoo.com>\nSigned-off-by: Finn Thain <fthain@telegraphics.com.au>\nAcked-by: Laurent Vivier <lvivier@redhat.com>\nReviewed-by: Geert Uytterhoeven <geert@linux-m68k.org>\nSigned-off-by: Jens Axboe <axboe@kernel.dk>","distinct":false,"url":"https://api.github.com/repos/masahir0y/linux-yamada/commits/7ae6a2b6cc058005ee3d0d2b9ce27688e51afa4b"},{"sha":"c1d6207cc0eef2a7f8551f9c7420d8776268f6e1","author":{"name":"Finn Thain","email":"94052abb058aed443995dc4f8d236e022112765d@telegraphics.com.au"},"message":"block/swim: Remove extra put_disk() call from error path\n\nCc: Laurent Vivier <lvivier@redhat.com>\nCc: Jens Axboe <axboe@kernel.dk>\nCc: stable@vger.kernel.org # v4.14+\nFixes: 103db8b2dfa5 (\"[PATCH] swim: stop sharing request queue across multiple gendisks\")\nTested-by: Stan Johnson <userm57@yahoo.com>\nSigned-off-by: Finn Thain <fthain@telegraphics.com.au>\nAcked-by: Laurent Vivier <lvivier@redhat.com>\nReviewed-by: Geert Uytterhoeven <geert@linux-m68k.org>\nSigned-off-by: Jens Axboe <axboe@kernel.dk>","distinct":false,"url":"https://api.github.com/repos/masahir0y/linux-yamada/commits/c1d6207cc0eef2a7f8551f9c7420d8776268f6e1"},{"sha":"8e2ab5a4efaac77fb93e5b5b109d0b3976fdd3a0","author":{"name":"Finn Thain","email":"94052abb058aed443995dc4f8d236e022112765d@telegraphics.com.au"},"message":"block/swim: Don't log an error message for an invalid ioctl\n\nThe 'eject' shell command may send various different ioctl commands.\nThis leads to error messages on the console even though the FDEJECT\nioctl succeeds.\n\n~# eject floppy\nSWIM floppy_ioctl: unknown cmd 21257\nSWIM floppy_ioctl: unknown cmd 1\n\nDon't log an error message for an invalid ioctl, just do as the\nswim3 driver does and return -ENOTTY.\n\nCc: Laurent Vivier <lvivier@redhat.com>\nCc: Jens Axboe <axboe@kernel.dk>\nCc: stable@vger.kernel.org # v4.14+\nTested-by: Stan Johnson <userm57@yahoo.com>\nSigned-off-by: Finn Thain <fthain@telegraphics.com.au>\nAcked-by: Laurent Vivier <lvivier@redhat.com>\nReviewed-by: Geert Uytterhoeven <geert@linux-m68k.org>\nSigned-off-by: Jens Axboe <axboe@kernel.dk>","distinct":false,"url":"https://api.github.com/repos/masahir0y/linux-yamada/commits/8e2ab5a4efaac77fb93e5b5b109d0b3976fdd3a0"},{"sha":"56a1c5ee54f69dd767fb61d301883dc919ddc259","author":{"name":"Finn Thain","email":"94052abb058aed443995dc4f8d236e022112765d@telegraphics.com.au"},"message":"block/swim: Rename macros to avoid inconsistent inverted logic\n\nThe Sony drive status bits use active-low logic. The swim_readbit()\nfunction converts that to 'C' logic for readability. Hence, the\nsense of the names of the status bit macros should not be inverted.\n\nMostly they are correct. However, the TWOMEG_DRIVE, MFM_MODE and\nTWOMEG_MEDIA macros have inverted sense (like MkLinux). Fix this\ninconsistency and make the following patches less confusing.\n\nThe same problem affects swim3.c so fix that too.\n\nNo functional change.\n\nThe FDHD drive status bits are documented in sonydriv.cpp from MAME\nand in swimiii.h from MkLinux.\n\nCc: Laurent Vivier <lvivier@redhat.com>\nCc: Benjamin Herrenschmidt <benh@kernel.crashing.org>\nCc: linuxppc-dev@lists.ozlabs.org\nCc: Jens Axboe <axboe@kernel.dk>\nCc: stable@vger.kernel.org # v4.14+\nTested-by: Stan Johnson <userm57@yahoo.com>\nSigned-off-by: Finn Thain <fthain@telegraphics.com.au>\nAcked-by: Laurent Vivier <lvivier@redhat.com>\nSigned-off-by: Jens Axboe <axboe@kernel.dk>","distinct":false,"url":"https://api.github.com/repos/masahir0y/linux-yamada/commits/56a1c5ee54f69dd767fb61d301883dc919ddc259"},{"sha":"8a500df63d07d8aee44b7ee2c54e462e47ce93ec","author":{"name":"Finn Thain","email":"94052abb058aed443995dc4f8d236e022112765d@telegraphics.com.au"},"message":"block/swim: Check drive type\n\nThe SWIM chip is compatible with GCR-mode Sony 400K/800K drives but\nthis driver only supports MFM mode. Therefore only Sony FDHD drives\nare supported. Skip incompatible drives.\n\nCc: Laurent Vivier <lvivier@redhat.com>\nCc: Jens Axboe <axboe@kernel.dk>\nCc: stable@vger.kernel.org # v4.14+\nTested-by: Stan Johnson <userm57@yahoo.com>\nSigned-off-by: Finn Thain <fthain@telegraphics.com.au>\nAcked-by: Laurent Vivier <lvivier@redhat.com>\nSigned-off-by: Jens Axboe <axboe@kernel.dk>","distinct":false,"url":"https://api.github.com/repos/masahir0y/linux-yamada/commits/8a500df63d07d8aee44b7ee2c54e462e47ce93ec"},{"sha":"5a13388d7aa1177b98d7168330ecbeeac52f844d","author":{"name":"Finn Thain","email":"94052abb058aed443995dc4f8d236e022112765d@telegraphics.com.au"},"message":"block/swim: Fix IO error at end of medium\n\nReading to the end of a 720K disk results in an IO error instead of EOF\nbecause the block layer thinks the disk has 2880 sectors. (Partly this\nis a result of inverted logic of the ONEMEG_MEDIA bit that's now fixed.)\n\nInitialize the density and head count in swim_add_floppy() to agree\nwith the device size passed to set_capacity() during drive probe.\n\nCall set_capacity() again upon device open, after refreshing the density\nand head count values.\n\nCc: Laurent Vivier <lvivier@redhat.com>\nCc: Jens Axboe <axboe@kernel.dk>\nCc: stable@vger.kernel.org # v4.14+\nTested-by: Stan Johnson <userm57@yahoo.com>\nSigned-off-by: Finn Thain <fthain@telegraphics.com.au>\nAcked-by: Laurent Vivier <lvivier@redhat.com>\nSigned-off-by: Jens Axboe <axboe@kernel.dk>","distinct":false,"url":"https://api.github.com/repos/masahir0y/linux-yamada/commits/5a13388d7aa1177b98d7168330ecbeeac52f844d"},{"sha":"b3906535ccc6cd04c42f9b1c7e31d1947b3ebc74","author":{"name":"Finn Thain","email":"94052abb058aed443995dc4f8d236e022112765d@telegraphics.com.au"},"message":"block/swim: Select appropriate drive on device open\n\nThe driver supports internal and external FDD units so the floppy_open\nfunction must not hard-code the drive location.\n\nCc: Laurent Vivier <lvivier@redhat.com>\nCc: Jens Axboe <axboe@kernel.dk>\nCc: stable@vger.kernel.org # v4.14+\nTested-by: Stan Johnson <userm57@yahoo.com>\nSigned-off-by: Finn Thain <fthain@telegraphics.com.au>\nAcked-by: Laurent Vivier <lvivier@redhat.com>\nSigned-off-by: Jens Axboe <axboe@kernel.dk>","distinct":false,"url":"https://api.github.com/repos/masahir0y/linux-yamada/commits/b3906535ccc6cd04c42f9b1c7e31d1947b3ebc74"},{"sha":"f4560231ec42092c6662acccabb28c6cac9f5dfb","author":{"name":"Jianchao Wang","email":"fda810c94eff99e385ce24487a739c8e85c32ed2@oracle.com"},"message":"blk-mq: start request gstate with gen 1\n\nrq->gstate and rq->aborted_gstate both are zero before rqs are\nallocated. If we have a small timeout, when the timer fires,\nthere could be rqs that are never allocated, and also there could\nbe rq that has been allocated but not initialized and started. At\nthe moment, the rq->gstate and rq->aborted_gstate both are 0, thus\nthe blk_mq_terminate_expired will identify the rq is timed out and\ninvoke .timeout early.\n\nFor scsi, this will cause scsi_times_out to be invoked before the\nscsi_cmnd is not initialized, scsi_cmnd->device is still NULL at\nthe moment, then we will get crash.\n\nCc: Bart Van Assche <bart.vanassche@wdc.com>\nCc: Tejun Heo <tj@kernel.org>\nCc: Ming Lei <ming.lei@redhat.com>\nCc: Martin Steigerwald <Martin@Lichtvoll.de>\nCc: stable@vger.kernel.org\nSigned-off-by: Jianchao Wang <jianchao.w.wang@oracle.com>\nSigned-off-by: Jens Axboe <axboe@kernel.dk>","distinct":false,"url":"https://api.github.com/repos/masahir0y/linux-yamada/commits/f4560231ec42092c6662acccabb28c6cac9f5dfb"},{"sha":"5db8f8d1099bd93a64a80b609dbcce887327ffc8","author":{"name":"Loic Poulain","email":"7dbc6498a90ff1ada42fc224430b4f763baa5c5c@linaro.org"},"message":"PCI: kirin: Fix reset gpio name\n\nAs documented in the devicetree bindings (pci/kirin-pcie.txt) and the\nreset gpio name must be 'reset-gpios'. However, current driver\nerroneously looks for a 'reset-gpio' resource which makes the driver\nprobe fail. Fix it.\n\nFixes: fc5165db245a (\"PCI: kirin: Add HiSilicon Kirin SoC PCIe controller driver\")\nSigned-off-by: Loic Poulain <loic.poulain@linaro.org>\n[lorenzo.pieralisi@arm.com: updated the commit log]\nSigned-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>\nAcked-by: Xiaowei Song <songxiaowei@hisilicon.com>","distinct":false,"url":"https://api.github.com/repos/masahir0y/linux-yamada/commits/5db8f8d1099bd93a64a80b609dbcce887327ffc8"},{"sha":"72961c4e6082be79825265d9193272b8a1634dec","author":{"name":"Jens Axboe","email":"cd8c6775e60d6f67a6984377324e5290df3d5358@kernel.dk"},"message":"bfq-iosched: ensure to clear bic/bfqq pointers when preparing request\n\nEven if we don't have an IO context attached to a request, we still\nneed to clear the priv[0..1] pointers, as they could be pointing\nto previously used bic/bfqq structures. If we don't do so, we'll\neither corrupt memory on dispatching a request, or cause an\nimbalance in counters.\n\nInspired by a fix from Kees.\n\nReported-by: Oleksandr Natalenko <oleksandr@natalenko.name>\nReported-by: Kees Cook <keescook@chromium.org>\nCc: stable@vger.kernel.org\nFixes: aee69d78dec0 (\"block, bfq: introduce the BFQ-v0 I/O scheduler as an extra scheduler\")\nSigned-off-by: Jens Axboe <axboe@kernel.dk>","distinct":false,"url":"https://api.github.com/repos/masahir0y/linux-yamada/commits/72961c4e6082be79825265d9193272b8a1634dec"},{"sha":"9de4ee40547fd315d4a0ed1dd15a2fa3559ad707","author":{"name":"Dan Carpenter","email":"ff341aa343d564f9e53e9dcb6996be8c04859a66@oracle.com"},"message":"cdrom: information leak in cdrom_ioctl_media_changed()\n\nThis cast is wrong.  \"cdi->capacity\" is an int and \"arg\" is an unsigned\nlong.  The way the check is written now, if one of the high 32 bits is\nset then we could read outside the info->slots[] array.\n\nThis bug is pretty old and it predates git.\n\nReviewed-by: Christoph Hellwig <hch@lst.de>\nCc: stable@vger.kernel.org\nSigned-off-by: Dan Carpenter <dan.carpenter@oracle.com>\nSigned-off-by: Jens Axboe <axboe@kernel.dk>","distinct":false,"url":"https://api.github.com/repos/masahir0y/linux-yamada/commits/9de4ee40547fd315d4a0ed1dd15a2fa3559ad707"},{"sha":"0ce9144471de9ee09306ca0127e7cd27521ccc3f","author":{"name":"Dave Chinner","email":"4d9e23a041ac966f5316a7481300d4ae12e806fe@redhat.com"},"message":"block: add blk_queue_fua() helper function\n\nSo we can check FUA support status from the iomap direct IO code.\n\nReviewed-by: Christoph Hellwig <hch@lst.de>\nSigned-off-by: Dave Chinner <dchinner@redhat.com>\nSigned-off-by: Jens Axboe <axboe@kernel.dk>","distinct":false,"url":"https://api.github.com/repos/masahir0y/linux-yamada/commits/0ce9144471de9ee09306ca0127e7cd27521ccc3f"}]}
{"actor":{"display_login":"masahir0y"}}