Re: kernel BUG at fs/lockd/mon.c:150, was Re: [PATCH v2 3/3] lockd: create and ...

2012-11-02 Thread Kees Bakker
On 30-10-12 14:04, Kees Bakker wrote: On 18-09-12 11:37, Stanislav Kinsbursky wrote: NSM RPC client can be required on NFSv3 umount, when child reaper is dying (and destroying it's mount namespace). It means, that current nsproxy is set to NULL already, but creation of RPC client requires UTS na

Re: kernel BUG at fs/lockd/mon.c:150, was Re: [PATCH v2 3/3] lockd: create and ...

2012-10-30 Thread Kees Bakker
On 30-10-12 14:04, Kees Bakker wrote: On 18-09-12 11:37, Stanislav Kinsbursky wrote: NSM RPC client can be required on NFSv3 umount, when child reaper is dying (and destroying it's mount namespace). It means, that current nsproxy is set to NULL already, but creation of RPC client requires UTS na

kernel BUG at fs/lockd/mon.c:150, was Re: [PATCH v2 3/3] lockd: create and ...

2012-10-30 Thread Kees Bakker
On 18-09-12 11:37, Stanislav Kinsbursky wrote: NSM RPC client can be required on NFSv3 umount, when child reaper is dying (and destroying it's mount namespace). It means, that current nsproxy is set to NULL already, but creation of RPC client requires UTS namespace for gaining hostname string. T