Re: Resource leak in unshare

From: Dmitry Vyukov
Date: Tue Nov 03 2015 - 03:48:51 EST

On Mon, Nov 2, 2015 at 8:01 PM, Eric W. Biederman <ebiederm@xxxxxxxxxxxx> wrote:
> Dmitry Vyukov <dvyukov@xxxxxxxxxx> writes:
>> Hello,
>> I am hitting the following warnings on
>> bcee19f424a0d8c26ecf2607b73c690802658b29 (4.3):
> Do you have any trace of the earlier failures?
> This appears to be something caused by an earlier failure (possibly
> whatever fails to allocate memory). Having network devices present
> but being in the generic cleanup routines is wrong.
> If there is no additional information can you please rerun with the
> following change applied? That should at least report which function is
> failing, and give us a good clue where to start debugging this.

So is it all fixed now? Or it is still clear how it can happen?
Eric (Dumazet), do you see how the WARNING can fire?
I don't have any logs at the moment, but I can run fuzzer for longer
to reproduce it again if necessary.

> diff --git a/net/core/net_namespace.c b/net/core/net_namespace.c
> index 2c2eb1b629b1..125c94af22b8 100644
> --- a/net/core/net_namespace.c
> +++ b/net/core/net_namespace.c
> @@ -292,6 +292,7 @@ out:
> return error;
> out_undo:
> + WARN(1, "net ops->init %pF returned with %d\n", ops->init, error);
> /* Walk through the list backwards calling the exit functions
> * for the pernet modules whose init functions did not fail.
> */
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at