Re: [PATCH] blk-mq: Fix recently introduced races in the timeout handling code

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: linux-block@xxxxxxxxxxxxxxx
Subject: Re: [PATCH] blk-mq: Fix recently introduced races in the timeout handling code
From: "Alex G." <mr.nuke.me@xxxxxxxxx>
Date: Tue, 10 Apr 2018 10:37:08 -0500
Cc: linux-nvme@xxxxxxxxxxxxxxxxxxx, austin_bolen@xxxxxxxx, Alex_Gagniuc@xxxxxxxxxxxx, shyam_iyer@xxxxxxxx, Keith Busch <keith.busch@xxxxxxxxx>, Scott Bauer <scott.bauer@xxxxxxxxx>
In-reply-to:
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0

I've observed a very nasty NULL pointer dereference with NVME drives on
hot-unplug [1]. While I haven't gone in the details of this change, it
does fix the NULL dereference I've been seeing.

Alex

[1] http://lists.infradead.org/pipermail/linux-nvme/2018-April/016623.html

Prev by Date: Re: [PATCH v4] blk-mq: Fix race conditions in request timeout handling
Next by Date: Re: [PATCH v4] blk-mq: Fix race conditions in request timeout handling
Previous by thread: Re: [PATCH] blk-mq: Fix recently introduced races in the timeout handling code
Next by thread: [PATCH] blk-throttle: only update last_low_overflow_time when LIMIT_MAX
Index(es):
- Date
- Thread

[Index of Archives] [Linux RAID] [Linux SCSI] [Linux ATA RAID] [IDE] [Linux Wireless] [Linux Kernel] [ATH6KL] [Linux Bluetooth] [Linux Netdev] [Kernel Newbies] [Security] [Git] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Device Mapper]

Powered by Linux