Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1657512
| From | Rakesh Pandit <rakesh@tuxera.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH V2] nvme: fix nvme_remove going to uninterruptible sleep for ever |
| Date | 2017-06-05 13:00 +0200 |
| Message-ID | <tOXTP-1Ok-1@gated-at.bofh.it> (permalink) |
| References | (1 earlier) <tMMpP-63R-11@gated-at.bofh.it> <tMQjM-8vK-17@gated-at.bofh.it> <tNwM1-21A-3@gated-at.bofh.it> <tOFDz-6V2-3@gated-at.bofh.it> <tOVoZ-nU-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Mon, Jun 05, 2017 at 10:18:17AM +0200, Christoph Hellwig wrote: > On Sun, Jun 04, 2017 at 06:28:15PM +0300, Sagi Grimberg wrote: > > > >> I think we need the NVME_CTRL_SCHED_RESET state. In fact I'm pretty > >> sure some time in the past I already had it in a local tree as a > >> generalization of rdma and loop already use NVME_CTRL_RESETTING > >> (they set it before queueing the reset work). > > > > I don't remember having it, but I might be wrong... > > > > Can you explain again why you think we need it? Sorry for being > > difficult, but I'm not exactly sure why it makes things better > > or simpler. > > Motly that we can treat a controller as under reset before scheduling > the reset work, both to prevent multiple schedules, and to make > checks like the one in nvme_should_reset robus. > > But I think something along the lines of the earlier patch from > Rakesh that just sets the RESETTING state earlier + the cancel_work_sync > suggested by you should also work for that purpose. So maybe that's > the way to go after all. I would post a new patch which includes my RESETTING state earlier patch + the cancel_work_sync which Sagi suggested after testing. Sagi: Because my RESETTING patch earlier is subset of your untested patch with cancel_work_sync, it would be logical to take a signed off from you as well. May you review/ack/nack the patch? Feel free to let me know if you want me to change it further or instead you want to post as author. I am okay with either as long as we fix the issue.
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH V2] nvme: fix nvme_remove going to uninterruptible sleep for ever Rakesh Pandit <rakesh@tuxera.com> - 2017-05-30 09:20 +0200
Re: [PATCH V2] nvme: fix nvme_remove going to uninterruptible sleep for ever Christoph Hellwig <hch@lst.de> - 2017-05-30 11:40 +0200
Re: [PATCH V2] nvme: fix nvme_remove going to uninterruptible sleep for ever Sagi Grimberg <sagi@grimberg.me> - 2017-05-30 12:20 +0200
Re: [PATCH V2] nvme: fix nvme_remove going to uninterruptible sleep for ever Rakesh Pandit <rakesh@tuxera.com> - 2017-05-30 16:30 +0200
Re: [PATCH V2] nvme: fix nvme_remove going to uninterruptible sleep for ever Christoph Hellwig <hch@lst.de> - 2017-06-01 13:50 +0200
Re: [PATCH V2] nvme: fix nvme_remove going to uninterruptible sleep for ever Rakesh Pandit <rakesh@tuxera.com> - 2017-06-01 14:30 +0200
Re: [PATCH V2] nvme: fix nvme_remove going to uninterruptible sleep for ever Christoph Hellwig <hch@lst.de> - 2017-06-01 14:40 +0200
Re: [PATCH V2] nvme: fix nvme_remove going to uninterruptible sleep for ever Rakesh Pandit <rakesh@tuxera.com> - 2017-06-01 14:40 +0200
Re: [PATCH V2] nvme: fix nvme_remove going to uninterruptible sleep for ever Christoph Hellwig <hch@lst.de> - 2017-06-01 14:50 +0200
Re: [PATCH V2] nvme: fix nvme_remove going to uninterruptible sleep for ever Ming Lei <ming.lei@redhat.com> - 2017-06-01 17:00 +0200
Re: [PATCH V2] nvme: fix nvme_remove going to uninterruptible sleep for ever Rakesh Pandit <rakesh@tuxera.com> - 2017-06-01 21:40 +0200
Re: [PATCH V2] nvme: fix nvme_remove going to uninterruptible sleep for ever Ming Lei <ming.lei@redhat.com> - 2017-06-02 03:50 +0200
Re: [PATCH V2] nvme: fix nvme_remove going to uninterruptible sleep for ever Sagi Grimberg <sagi@grimberg.me> - 2017-06-04 17:30 +0200
Re: [PATCH V2] nvme: fix nvme_remove going to uninterruptible sleep for ever Christoph Hellwig <hch@lst.de> - 2017-06-05 10:20 +0200
Re: [PATCH V2] nvme: fix nvme_remove going to uninterruptible sleep for ever Rakesh Pandit <rakesh@tuxera.com> - 2017-06-05 13:00 +0200
Re: [PATCH V2] nvme: fix nvme_remove going to uninterruptible sleep for ever Sagi Grimberg <sagi@grimberg.me> - 2017-06-05 13:10 +0200
csiph-web