linux-kernel - Re: [PATCH V2] nvme: fix multiple ctrl removal scheduling

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <7a49d9eb-2a46-dc8f-7284-b71c843cce8e@grimberg.me>
Date:   Mon, 5 Jun 2017 20:19:54 +0300
From:   Sagi Grimberg <sagi@...mberg.me>
To:     Rakesh Pandit <rakesh@...era.com>, linux-nvme@...ts.infradead.org,
        linux-kernel@...r.kernel.org
Cc:     Keith Busch <keith.busch@...el.com>, Jens Axboe <axboe@...com>,
        Christoph Hellwig <hch@....de>
Subject: Re: [PATCH V2] nvme: fix multiple ctrl removal scheduling


> 
> V2: 1. Use cancel_work_sync instead of introducing new state (Sagi)
>      2. Skip using NVME_CTRL_SCHED_RESET state (Sagi)
> V1: nvme_probe set RESETTING state and check for NVME_CTRL_RESETTING
>      state in nvme_should_reset instead of work_busy (hch)

This type of information should come after the '---' separator
so git history won't keep it forever.

> Fixes: c5f6ce97c1210 ("nvme: don't schedule multiple resets")
> Signed-off-by: Rakesh Pandit <rakesh@...era.com>
> ---
Other than that,

Reviewed-by: Sagi Grimberg <sagi@...mberg.me>