Created attachment 256483 [details]
customizable lock timeout
The 30 seconds sleep time between two lock release recheck in case of F_SETLKW it might be OK for real network shares, but if it used to export directory from host to guest, it is too big. So, the attached patch adds an option that can be specified at mount time so the wait time sent to schedule_timeout_interruptible can be customized. It defaults to the value of P9_LOCK_TIMEOUT.
Created attachment 278313 [details]
same diff formatted as a patch
I have no problem with that one, I'd like to post it almost as is under your name but I don't think I can do that because you just posted a diff and not a patch with a Signed-off-by tag.
I've attached the same diff as a patch with the following changes:
- cast option * HZ to long to avoid int truncation (thanks C)
- adjusted the wording of the new v9ses field comment
- a commit message
could you please reupload the same patch with an extra ligne "Signed-off-by: your name <your mail>", or send it to the following after adding the line (output of get_maintainers.pl) via git send-email? (If you reattach it, I will just send the mail for you)
Feel free to adjust wording/whatever at the same time.
$ ./scripts/get_maintainer.pl < 0001-9p-locks-add-mount-option-for-lock-retry-interval.patch
Eric Van Hensbergen <firstname.lastname@example.org> (maintainer:9P FILE SYSTEM)
Latchesar Ionkov <email@example.com> (maintainer:9P FILE SYSTEM)
Dominique Martinet <firstname.lastname@example.org> (maintainer:9P FILE SYSTEM)
email@example.com (open list:9P FILE SYSTEM)
firstname.lastname@example.org (open list)
Created attachment 278361 [details]
patch with Signed-off-by:
Thanks, I've just sent the patch to the kernel lists.
As said there, I'll queue it up to linux-next around next week, and should get that merged for 2.20 (so in linus' master branch early November at the start of next cycle)
Thank you for the support.