Re: [PATCH] mpt3sas: Do not mark fw_event workqueue as WQ_MEM_RECLAIM

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

To: Hannes Reinecke <hare@xxxxxxx>
Subject: Re: [PATCH] mpt3sas: Do not mark fw_event workqueue as WQ_MEM_RECLAIM
From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
Date: Thu, 01 Mar 2018 20:39:26 -0500
Cc: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>, Christoph Hellwig <hch@xxxxxx>, James Bottomley <james.bottomley@xxxxxxxxxxxxxxxxxxxxx>, linux-scsi@xxxxxxxxxxxxxxx, Sreekanth Reddy <sreekanth.reddy@xxxxxxxxxxxx>, Suganath Prabu Subramani <suganath-prabu.subramani@xxxxxxxxxxxx>, Hannes Reinecke <hare@xxxxxxxx>
In-reply-to: <20180226142601.110639-1-hare@suse.de> (Hannes Reinecke's message of "Mon, 26 Feb 2018 15:26:01 +0100")
Organization: Oracle Corporation
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux)

Hannes,

> The firmware event workqueue should not be marked as WQ_MEM_RECLAIM as
> it's doesn't need to make forward progress under memory pressure.  In
> the current state it will result in a deadlock if the device had been
> forcefully removed.

Applied to 4.16/scsi-fixes. Thanks!

-- 
Martin K. Petersen	Oracle Linux Engineering

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

References:
- [PATCH] mpt3sas: Do not mark fw_event workqueue as WQ_MEM_RECLAIM
  - From: Hannes Reinecke

Prev by Date: Re: [PATCH] qla2xxx: Fix NULL pointer crash due to active timer for ABTS
Next by Date: Re: [PATCH V2] scsi: core: use blk_mq_requeue_request in __scsi_queue_insert
Previous by thread: RE: [PATCH] mpt3sas: Do not mark fw_event workqueue as WQ_MEM_RECLAIM
Next by thread: Re: [bug report] Don't enter SCSI error handler on kernel 4.16-rc1
Index(es):
- Date
- Thread

[Index of Archives] [SCSI Target Devel] [Linux SCSI Target Infrastructure] [Kernel Newbies] [IDE] [Security] [Git] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Linux ATA RAID] [Linux IIO] [Samba] [Device Mapper]