On Mon, Jul 11, 2016 at 4:52 PM, Weston Andros Adamson <dros@xxxxxxxxxx> wrote: > >> On Jul 11, 2016, at 9:47 AM, Alexey Dobriyan <adobriyan@xxxxxxxxx> wrote: >> >> On Mon, Jul 11, 2016 at 4:28 PM, Trond Myklebust >> <trondmy@xxxxxxxxxxxxxxx> wrote: >>> >>>> On Jul 11, 2016, at 08:59, Alexey Dobriyan <adobriyan@xxxxxxxxx> wrote: >>>> >>>> We have a customer who was able to reliably reproduce the following hang: >>>> (hang itself is rare but there are many machines, so it is not rare) >>>> >>>> INFO: task ascp:66692 blocked for more than 120 seconds. >>> >>> Why is this being reported here and not to Red Hat? Is the bug reproducible on the upstream kernel? >> >> It is not a report per se, more heads up for other folks like CentOS >> and other rebuilders. >> I checked every NFS commit since 3.10, there seems to be nothing fixing it. >> As for testing mainline, I don't know, maybe we can arrange that. >> >> Alexey >> > > How have you checked every commit since 3.10 and not tested "mainline"? > > I don't get how both can be true. Do you mean you manually inspected each > commit? I'm not sure the fix would be so obvious... I've looked at commits. If the bug was fixed accidentally, then sorry for the noise. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
