messages from 2018-04-06 14:26:49 to 2018-04-10 21:54:56 UTC [more...]
[PATCH v4] blk-mq: Fix race conditions in request timeout handling
2018-04-10 21:54 UTC (26+ messages)
[PATCH v5] blk-mq: Avoid that a completion can be ignored for BLK_EH_RESET_TIMER
2018-04-10 21:01 UTC
[BISECTED][REGRESSION] Hang while booting EeePC 900
2018-04-10 20:46 UTC (4+ messages)
` [PATCH] blk-mq: Directly schedule q->timeout_work when aborting a request
[PATCH v2] blk-mq: Avoid that submitting a bio concurrently with device removal triggers a crash
2018-04-10 20:45 UTC
[PATCH] blk-mq: Avoid that submitting a bio concurrently with device removal triggers a crash
2018-04-10 20:30 UTC
Hotplug
2018-04-10 17:17 UTC
usercopy whitelist woe in scsi_sense_cache
2018-04-10 17:16 UTC (11+ messages)
Hang with blk-mq map series (block/008)
2018-04-10 15:51 UTC
[PATCH] blk-mq: Fix recently introduced races in the timeout handling code
2018-04-10 15:37 UTC
[RFC] fix confusion around GFP_* flags and blk_get_request
2018-04-10 6:29 UTC (17+ messages)
` [PATCH 1/7] scsi/osd: remove the gfp argument to osd_start_request
` [PATCH 2/7] block: fix __get_request documentation
` [PATCH 3/7] block: sanitize blk_get_request calling conventions
` [PATCH 4/7] block: pass explicit gfp_t to get_request
` [PATCH 5/7] block: use GFP_NOIO instead of __GFP_DIRECT_RECLAIM
` [PATCH 6/7] block: consistently use GFP_NOIO instead of __GFP_NORECLAIM
` [PATCH 7/7] block: use GFP_KERNEL for allocations from blk_get_request
[block regression] kernel oops triggered by removing scsi device dring IO
2018-04-10 1:34 UTC (15+ messages)
limits->max_sectors is getting set to 0, why/where? [was: Re: dm: kernel oops by divide error on v4.16+]
2018-04-10 0:31 UTC (14+ messages)
4.15.14 crash with iscsi target and dvd
2018-04-09 23:51 UTC (22+ messages)
[s390x] New regression was found on kernel-4.16
2018-04-09 23:02 UTC
[PATCH v2] blk-cgroup: remove entries in blkg_tree before queue release
2018-04-09 22:09 UTC (2+ messages)
[PATCH] blk-mq: Fix recently introduced races in the timeout handling code
2018-04-09 21:40 UTC (13+ messages)
Block layer use of __GFP flags
2018-04-09 17:31 UTC (11+ messages)
Multi-Actuator SAS HDD First Look
2018-04-09 16:02 UTC (14+ messages)
[PATCH 0/8] blk-mq: fix and improve queue mapping
2018-04-09 15:48 UTC (28+ messages)
` [PATCH 1/8] blk-mq: make sure that correct hctx->next_cpu is set
` [PATCH 2/8] blk-mq: don't keep offline CPUs mapped to hctx 0
` [PATCH 3/8] blk-mq: avoid to write intermediate result to hctx->next_cpu
` [PATCH 4/8] blk-mq: introduce blk_mq_hw_queue_first_cpu() to figure out first cpu
` [PATCH 5/8] blk-mq: remove blk_mq_delay_queue()
` [PATCH 6/8] blk-mq: don't check queue mapped in __blk_mq_delay_run_hw_queue()
` [PATCH 7/8] blk-mq: reimplement blk_mq_hw_queue_mapped
` [PATCH 8/8] blk-mq: remove code for dealing with remapping queue
BUG at IP: blk_mq_get_request+0x23e/0x390 on 4.16.0-rc7
2018-04-09 12:15 UTC (17+ messages)
[PATCH] blk-throttle: only update last_low_overflow_time when LIMIT_MAX
2018-04-09 6:16 UTC
[PATCH] blk-throttle: discard stale last_low_overflow_time
2018-04-09 6:15 UTC
KASAN: use-after-free Read in disk_unblock_events
2018-04-08 18:21 UTC (2+ messages)
[PATCH] blk-throttle: fix typo in blkg_print_stat_ios() comments
2018-04-08 9:01 UTC
[PATCH V3 0/4] genirq/affinity: irq vector spread among online CPUs as far as possible
2018-04-08 3:19 UTC (11+ messages)
` [PATCH V3 4/4] "
[PATCH] loop: fix LOOP_GET_STATUS lock imbalance
2018-04-07 10:55 UTC (5+ messages)
[RFC PATCH 0/2] use larger max_request_size for virtio_blk
2018-04-07 8:30 UTC (3+ messages)
[PATCH] blk-cgroup: remove entries in blkg_tree before queue release
2018-04-06 23:24 UTC (3+ messages)
[PATCH] block/compat_ioctl: fix range check in BLKGETSIZE
2018-04-06 22:23 UTC
[PATCH] blk-mq: only run mapped hw queues in blk_mq_run_hw_queues()
2018-04-06 15:40 UTC (15+ messages)
WARNING: lock held when returning to user space!
2018-04-06 15:01 UTC (4+ messages)
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).