On 2016/02/18 0:11, David Sterba wrote:
On Wed, Feb 17, 2016 at 02:54:23PM +0900, Satoru Takeuchi wrote:
On 2016/02/16 2:53, David Sterba wrote:
On Mon, Feb 15, 2016 at 02:38:09PM +0900, Satoru Takeuchi wrote:
There are some BUG_ON()'s after kmalloc() as follows.
=
foo = kmalloc();
On Wed, Feb 17, 2016 at 02:54:23PM +0900, Satoru Takeuchi wrote:
> On 2016/02/16 2:53, David Sterba wrote:
> > On Mon, Feb 15, 2016 at 02:38:09PM +0900, Satoru Takeuchi wrote:
> >> There are some BUG_ON()'s after kmalloc() as follows.
> >>
> >> =
> >> foo = kmalloc();
> >> BUG_ON(!foo);
On 2016/02/16 2:53, David Sterba wrote:
On Mon, Feb 15, 2016 at 02:38:09PM +0900, Satoru Takeuchi wrote:
There are some BUG_ON()'s after kmalloc() as follows.
=
foo = kmalloc();
BUG_ON(!foo); /* -ENOMEM case */
=
A Docker + memory cgroup user hit these BUG_ON()s.
On Mon, Feb 15, 2016 at 02:38:09PM +0900, Satoru Takeuchi wrote:
> There are some BUG_ON()'s after kmalloc() as follows.
>
> =
> foo = kmalloc();
> BUG_ON(!foo); /* -ENOMEM case */
> =
>
> A Docker + memory cgroup user hit these BUG_ON()s.
>
>
There are some BUG_ON()'s after kmalloc() as follows.
=
foo = kmalloc();
BUG_ON(!foo); /* -ENOMEM case */
=
A Docker + memory cgroup user hit these BUG_ON()s.
https://bugzilla.kernel.org/show_bug.cgi?id=112101
Since it's very hard to handle these ENOMEMs properly,
preventing these
