Re: [PATCH v5 0/8] block, scsi, md: Improve suspend and resume

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

 



On Wed, Oct 04, 2017 at 03:18:45PM +0000, Bart Van Assche wrote:
> On Wed, 2017-10-04 at 15:53 +0800, Ming Lei wrote:
> > I have commented on Bart's patchset before, but my comments
> > never gets addressed:
> > 
> > 1) no MD changes required on this issue
> 
> I did not address that comment because you have another view on how suspend
> and resume should work than the rest of the kernel community. See also the
> detailed explanation in https://marc.info/?l=linux-block&m=150695879309606.
> See also Luis' cover letter "[RFC 0/5] fs: replace kthread freezing with
> filesystem freeze/thaw" (https://marc.info/?l=linux-block&m=150705690302420).

That is still in discussion, and once SCSI quiesce is safe, these two
MD change isn't necessary, that is why my patchset focuses on making
SCSI quiesce safe only. That is why I suggest to not include these two
patches in this patchset, because isn't necessary simply.

I also replied Luis already.

> 
> > 2) RCU read lock is missed in fast path
> 
> Did you really post this as a review comment on my patch series? Anyway, this
> is easy to address.

https://marc.info/?l=linux-block&m=150641481732572&w=2


> 
> > 3) bad patch title:
> > 
> > - such as :  'scsi-mq: Reduce suspend latency'
> > 	this is very misleading since it is actually bug fix
> > 
> > - such as : "Make SCSI device suspend and resume work reliably"
> > 	also a bit not accurate
> 
> Same here - had you posted this as a review comment before? Anyway, this is
> also easy to address.

I have mentioned lots of times, the root cause is only in SCSI quiesce,
actually not related with suspend/resume directly. But you never
consider my comment, that is why you post out these patches with
wrong title(or very misleading) again and again.

> 
> > Also holding sdev->state_mutex before freezing queue might
> > cause deadlock since this lock can be acquired in eh handler(
> > scsi_eh_offline_sdevs())
> 
> Had you posted this as a comment before? Anyway, I will address this comment
> too.

This one is what I just posted out, so you see it isn't marked as 4).

-- 
Ming



[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