[Kernel-packages] [Bug 1650062] Re: Ubuntu16.04.01VM:Docker-Powervm aufs bad file panic while running tests in a docker container

2017-04-05 Thread bugproxy
** Tags removed: severity-critical ** Tags added: severity-high -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1650062 Title: Ubuntu16.04.01VM:Docker-Powervm aufs bad file panic while

[Kernel-packages] [Bug 1650062] Re: Ubuntu16.04.01VM:Docker-Powervm aufs bad file panic while running tests in a docker container

2017-01-23 Thread Manoj Iyer
** Changed in: linux (Ubuntu) Assignee: Taco Screen team (taco-screen-team) => Seth Forshee (sforshee) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1650062 Title:

[Kernel-packages] [Bug 1650062] Re: Ubuntu16.04.01VM:Docker-Powervm aufs bad file panic while running tests in a docker container

2017-01-23 Thread Seth Forshee
I haven't found any obvious source in aufs for the extra fputs which I suspect are causing this problem. If you could either give me more information so I can run the same tests myself (I'm guessing the problem isn't arch-specific) or else reproduce the problem with the kernel patched with

[Kernel-packages] [Bug 1650062] Re: Ubuntu16.04.01VM:Docker-Powervm aufs bad file panic while running tests in a docker container

2017-01-09 Thread Seth Forshee
>From the attachment file->f_inode is NULL. That shouldn't be the case for a file passed to the aufs flush callback, so it's not a bug for aufs to assume it will be non-NULL. However in this case the file has a negative reference count, so there must be some earlier problem with reference