/openbmc/linux/kernel/ |
H A D | utsname.c | df75e774 Thu Sep 22 13:08:36 CDT 2016 Eric W. Biederman <ebiederm@xmission.com> userns: When the per user per user namespace limit is reached return ENOSPC
The current error codes returned when a the per user per user namespace limit are hit (EINVAL, EUSERS, and ENFILE) are wrong. I asked for advice on linux-api and it we made clear that those were the wrong error code, but a correct effor code was not suggested.
The best general error code I have found for hitting a resource limit is ENOSPC. It is not perfect but as it is unambiguous it will serve until someone comes up with a better error code.
Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com> df75e774 Thu Sep 22 13:08:36 CDT 2016 Eric W. Biederman <ebiederm@xmission.com> userns: When the per user per user namespace limit is reached return ENOSPC The current error codes returned when a the per user per user namespace limit are hit (EINVAL, EUSERS, and ENFILE) are wrong. I asked for advice on linux-api and it we made clear that those were the wrong error code, but a correct effor code was not suggested. The best general error code I have found for hitting a resource limit is ENOSPC. It is not perfect but as it is unambiguous it will serve until someone comes up with a better error code. Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>
|
H A D | pid_namespace.c | df75e774 Thu Sep 22 13:08:36 CDT 2016 Eric W. Biederman <ebiederm@xmission.com> userns: When the per user per user namespace limit is reached return ENOSPC
The current error codes returned when a the per user per user namespace limit are hit (EINVAL, EUSERS, and ENFILE) are wrong. I asked for advice on linux-api and it we made clear that those were the wrong error code, but a correct effor code was not suggested.
The best general error code I have found for hitting a resource limit is ENOSPC. It is not perfect but as it is unambiguous it will serve until someone comes up with a better error code.
Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com> df75e774 Thu Sep 22 13:08:36 CDT 2016 Eric W. Biederman <ebiederm@xmission.com> userns: When the per user per user namespace limit is reached return ENOSPC The current error codes returned when a the per user per user namespace limit are hit (EINVAL, EUSERS, and ENFILE) are wrong. I asked for advice on linux-api and it we made clear that those were the wrong error code, but a correct effor code was not suggested. The best general error code I have found for hitting a resource limit is ENOSPC. It is not perfect but as it is unambiguous it will serve until someone comes up with a better error code. Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>
|
H A D | user_namespace.c | df75e774 Thu Sep 22 13:08:36 CDT 2016 Eric W. Biederman <ebiederm@xmission.com> userns: When the per user per user namespace limit is reached return ENOSPC
The current error codes returned when a the per user per user namespace limit are hit (EINVAL, EUSERS, and ENFILE) are wrong. I asked for advice on linux-api and it we made clear that those were the wrong error code, but a correct effor code was not suggested.
The best general error code I have found for hitting a resource limit is ENOSPC. It is not perfect but as it is unambiguous it will serve until someone comes up with a better error code.
Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com> df75e774 Thu Sep 22 13:08:36 CDT 2016 Eric W. Biederman <ebiederm@xmission.com> userns: When the per user per user namespace limit is reached return ENOSPC The current error codes returned when a the per user per user namespace limit are hit (EINVAL, EUSERS, and ENFILE) are wrong. I asked for advice on linux-api and it we made clear that those were the wrong error code, but a correct effor code was not suggested. The best general error code I have found for hitting a resource limit is ENOSPC. It is not perfect but as it is unambiguous it will serve until someone comes up with a better error code. Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>
|
/openbmc/linux/ipc/ |
H A D | namespace.c | df75e774 Thu Sep 22 13:08:36 CDT 2016 Eric W. Biederman <ebiederm@xmission.com> userns: When the per user per user namespace limit is reached return ENOSPC
The current error codes returned when a the per user per user namespace limit are hit (EINVAL, EUSERS, and ENFILE) are wrong. I asked for advice on linux-api and it we made clear that those were the wrong error code, but a correct effor code was not suggested.
The best general error code I have found for hitting a resource limit is ENOSPC. It is not perfect but as it is unambiguous it will serve until someone comes up with a better error code.
Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com> df75e774 Thu Sep 22 13:08:36 CDT 2016 Eric W. Biederman <ebiederm@xmission.com> userns: When the per user per user namespace limit is reached return ENOSPC The current error codes returned when a the per user per user namespace limit are hit (EINVAL, EUSERS, and ENFILE) are wrong. I asked for advice on linux-api and it we made clear that those were the wrong error code, but a correct effor code was not suggested. The best general error code I have found for hitting a resource limit is ENOSPC. It is not perfect but as it is unambiguous it will serve until someone comes up with a better error code. Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>
|
/openbmc/linux/fs/ |
H A D | namespace.c | df75e774 Thu Sep 22 13:08:36 CDT 2016 Eric W. Biederman <ebiederm@xmission.com> userns: When the per user per user namespace limit is reached return ENOSPC
The current error codes returned when a the per user per user namespace limit are hit (EINVAL, EUSERS, and ENFILE) are wrong. I asked for advice on linux-api and it we made clear that those were the wrong error code, but a correct effor code was not suggested.
The best general error code I have found for hitting a resource limit is ENOSPC. It is not perfect but as it is unambiguous it will serve until someone comes up with a better error code.
Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com> df75e774 Thu Sep 22 13:08:36 CDT 2016 Eric W. Biederman <ebiederm@xmission.com> userns: When the per user per user namespace limit is reached return ENOSPC The current error codes returned when a the per user per user namespace limit are hit (EINVAL, EUSERS, and ENFILE) are wrong. I asked for advice on linux-api and it we made clear that those were the wrong error code, but a correct effor code was not suggested. The best general error code I have found for hitting a resource limit is ENOSPC. It is not perfect but as it is unambiguous it will serve until someone comes up with a better error code. Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>
|
/openbmc/linux/net/core/ |
H A D | net_namespace.c | df75e774 Thu Sep 22 13:08:36 CDT 2016 Eric W. Biederman <ebiederm@xmission.com> userns: When the per user per user namespace limit is reached return ENOSPC
The current error codes returned when a the per user per user namespace limit are hit (EINVAL, EUSERS, and ENFILE) are wrong. I asked for advice on linux-api and it we made clear that those were the wrong error code, but a correct effor code was not suggested.
The best general error code I have found for hitting a resource limit is ENOSPC. It is not perfect but as it is unambiguous it will serve until someone comes up with a better error code.
Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com> df75e774 Thu Sep 22 13:08:36 CDT 2016 Eric W. Biederman <ebiederm@xmission.com> userns: When the per user per user namespace limit is reached return ENOSPC The current error codes returned when a the per user per user namespace limit are hit (EINVAL, EUSERS, and ENFILE) are wrong. I asked for advice on linux-api and it we made clear that those were the wrong error code, but a correct effor code was not suggested. The best general error code I have found for hitting a resource limit is ENOSPC. It is not perfect but as it is unambiguous it will serve until someone comes up with a better error code. Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>
|