Re: [BUG] task->nsproxy was unexpectedly NULL (caught in exit_shm)

[Cyrill Gorcunov]

On Sat, Feb 18, 2012 at 09:39:50PM +0400, Vasiliy Kulikov wrote:
...
> > 
> > So task->nsproxy was unexpectedly NULL atm.
> > The bug happened only once so far.
> 
> I'm confused.  How ->nsproxy can be NULL in do_exit()?  AFAIU, it is not a
> special process (i.e. init or udev), but a common chrome process.
> 
> Could it be missing get_nsproxy() somewhere?  And as a result, freed
> current->nsproxy while still having active users.
> 

Probably it would worth to repeat this issue without proprientary
drivers loaded. Also I wonder why don't we use rcu_assign_pointer
for nsproxy in copy_namespaces.

	Cyrill
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/