RFR: 8145981 (fs) LinuxWatchService can reports events against wrong directory
Sebastian Sickelmann
sebastian.sickelmann at gmx.de
Tue Dec 29 18:44:55 UTC 2015
On 12/29/2015 06:16 PM, Alan Bateman wrote:
>
>
> On 29/12/2015 15:27, Sebastian Sickelmann wrote:
>> :
>> I changed it to your solution. You are right the order of processing
>> pending events and new events from inotify do not need any guarantee. So
>> processing pending events (and shutdown) can be done later.
> Thanks, I think this is the easiest to maintain.
>
>
>> :
>> I updated the webrev and tried to reduce the time in the test by
>> generating more watch-keys. On my machine I am now always below 10 secs
>> and in most cases below 5 sec.
>>
>> http://cr.openjdk.java.net/~sebastian/8145981/webrev.01/
>>
> This looks okay. I'll run it on our build+test system to make sure
> that the test is passing on all platforms.
>
> -Alan
How does it work with a jdk8 backport? I think the issue-number 8145981
would be burned with this patch.
Should we create a new subtask of the issue for this jdk9 patch?
Here is a changeset for the case the original issue-number should be
used and everything goes ok with build and test.
http://cr.openjdk.java.net/~sebastian/8145981/webrev.02/jdk.changeset
--
Sebastian
More information about the nio-dev
mailing list