On Wed, Feb 19, 2020 at 12:21:55PM +0100, Anthony Mallet wrote: > On Wednesday 19 Feb 2020, at 10:56, Oliver Neukum wrote: > > thank you for the detailed report about an unusual bug. Could you > > test the attached patch? > > I did not actually run it yet, but at first sight it seems that it will > mishandle the ASYNC_CLOSING_WAIT_NONE case. > > I attach patch 0002 which should handle all cases. I also inverted the > logic of the CAP_SYS_ADMIN test, so that the delays are changed only > if the rounded values (in 1/100th of seconds) are actually changed. > > While I was there, I checked what other drivers do (it seems that many > have the same issue). Something I also noticed is that the units are > also maybe mishandled: internally the values seem to be in 'jiffies', > not in msecs. See for instance: > https://github.com/torvalds/linux/blob/701a9c8092ddf299d7f90ab2d66b19b4526d1186/drivers/tty/serial/serial_core.c#L780 > > So I added patch 0001 that uses the jiffies conversion functions. If > you prefer to discuss this in a separate thread please tell me, I will > redo just patch 0002 without this change. > > > > I have taken the liberty of presuming to add your 'Reported-and-tested-by'. > > Yes, no problem. Thank you. > I hope my patches follow the required format, I'm not sure about all > the details. Hi, This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him a patch that has triggered this response. He used to manually respond to these common problems, but in order to save his sanity (he kept writing the same thing over and over, yet to different people), I was created. Hopefully you will not take offence and will fix the problem in your patch and resubmit it so that it can be accepted into the Linux kernel tree. You are receiving this message because of the following common error(s) as indicated below: - Your patch was attached, please place it inline so that it can be applied directly from the email message itself. - Your patch does not have a Signed-off-by: line. Please read the kernel file, Documentation/SubmittingPatches and resend it after adding that line. Note, the line needs to be in the body of the email, before the patch, not at the bottom of the patch or in the email signature. If you wish to discuss this problem further, or you have questions about how to resolve this issue, please feel free to respond to this email and Greg will reply once he has dug out from the pending patches received from other developers. thanks, greg k-h's patch email bot
