>>
>> Thank you for the confirmation. Please include me in this thread if
>> someone
>> finds the answer. This bug seems to occur very frequently on my
>> machine with
>> 2.6.18.1 so I have been forced to revert back to 2.6.17.13 until I can
>> fix it.
>
> I haven't got around to looking at it yet, sorry.
>
> It does seem like my inotify scalability patch is involved, however it is
> interesting that you cannot reproduce the problem in 2.6.17.13.
>
> I probably won't get around to having a look at it for a while, but if you
> would like to speed up the process you could try running a git bisect to
> find which patch is making the error trigger for you.
>
I finally got around to try 2.6.18.2 and I still seem to have this problem. Has
anyone had a chance to make a patch for this yet?
Best Regards.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]