| /openbmc/linux/net/netfilter/ |
| H A D | xt_SECMARK.c | 15714f7b Tue Oct 12 10:40:08 CDT 2010 Eric Paris <eparis@redhat.com> secmark: do not return early if there was no error
Commit 4a5a5c73 attempted to pass decent error messages back to userspace for
netfilter errors. In xt_SECMARK.c however the patch screwed up and returned
on 0 (aka no error) early and didn't finish setting up secmark. This results
in a kernel BUG if you use SECMARK.
Signed-off-by: Eric Paris <eparis@redhat.com>
Acked-by: Paul Moore <paul.moore@hp.com>
Signed-off-by: James Morris <jmorris@namei.org>
4a5a5c73 Fri Mar 19 11:32:59 CDT 2010 Jan Engelhardt <jengelh@medozas.de> netfilter: xtables: slightly better error reporting
When extended status codes are available, such as ENOMEM on failed
allocations, or subsequent functions (e.g. nf_ct_get_l3proto), passing
them up to userspace seems like a good idea compared to just always
EINVAL.
Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
15714f7b Tue Oct 12 10:40:08 CDT 2010 Eric Paris <eparis@redhat.com> secmark: do not return early if there was no error
Commit 4a5a5c73 attempted to pass decent error messages back to userspace for
netfilter errors. In xt_SECMARK.c however the patch screwed up and returned
on 0 (aka no error) early and didn't finish setting up secmark. This results
in a kernel BUG if you use SECMARK.
Signed-off-by: Eric Paris <eparis@redhat.com>
Acked-by: Paul Moore <paul.moore@hp.com>
Signed-off-by: James Morris <jmorris@namei.org>
4a5a5c73 Fri Mar 19 11:32:59 CDT 2010 Jan Engelhardt <jengelh@medozas.de> netfilter: xtables: slightly better error reporting
When extended status codes are available, such as ENOMEM on failed
allocations, or subsequent functions (e.g. nf_ct_get_l3proto), passing
them up to userspace seems like a good idea compared to just always
EINVAL.
Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
|
| H A D | xt_HL.c | 4a5a5c73 Fri Mar 19 11:32:59 CDT 2010 Jan Engelhardt <jengelh@medozas.de> netfilter: xtables: slightly better error reporting
When extended status codes are available, such as ENOMEM on failed
allocations, or subsequent functions (e.g. nf_ct_get_l3proto), passing
them up to userspace seems like a good idea compared to just always
EINVAL.
Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
4a5a5c73 Fri Mar 19 11:32:59 CDT 2010 Jan Engelhardt <jengelh@medozas.de> netfilter: xtables: slightly better error reporting
When extended status codes are available, such as ENOMEM on failed
allocations, or subsequent functions (e.g. nf_ct_get_l3proto), passing
them up to userspace seems like a good idea compared to just always
EINVAL.
Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
|
| H A D | xt_DSCP.c | 4a5a5c73 Fri Mar 19 11:32:59 CDT 2010 Jan Engelhardt <jengelh@medozas.de> netfilter: xtables: slightly better error reporting
When extended status codes are available, such as ENOMEM on failed
allocations, or subsequent functions (e.g. nf_ct_get_l3proto), passing
them up to userspace seems like a good idea compared to just always
EINVAL.
Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
4a5a5c73 Fri Mar 19 11:32:59 CDT 2010 Jan Engelhardt <jengelh@medozas.de> netfilter: xtables: slightly better error reporting
When extended status codes are available, such as ENOMEM on failed
allocations, or subsequent functions (e.g. nf_ct_get_l3proto), passing
them up to userspace seems like a good idea compared to just always
EINVAL.
Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
|
| H A D | xt_statistic.c | 4a5a5c73 Fri Mar 19 11:32:59 CDT 2010 Jan Engelhardt <jengelh@medozas.de> netfilter: xtables: slightly better error reporting
When extended status codes are available, such as ENOMEM on failed
allocations, or subsequent functions (e.g. nf_ct_get_l3proto), passing
them up to userspace seems like a good idea compared to just always
EINVAL.
Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
4a5a5c73 Fri Mar 19 11:32:59 CDT 2010 Jan Engelhardt <jengelh@medozas.de> netfilter: xtables: slightly better error reporting
When extended status codes are available, such as ENOMEM on failed
allocations, or subsequent functions (e.g. nf_ct_get_l3proto), passing
them up to userspace seems like a good idea compared to just always
EINVAL.
Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
|
| H A D | xt_dscp.c | 4a5a5c73 Fri Mar 19 11:32:59 CDT 2010 Jan Engelhardt <jengelh@medozas.de> netfilter: xtables: slightly better error reporting
When extended status codes are available, such as ENOMEM on failed
allocations, or subsequent functions (e.g. nf_ct_get_l3proto), passing
them up to userspace seems like a good idea compared to just always
EINVAL.
Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
4a5a5c73 Fri Mar 19 11:32:59 CDT 2010 Jan Engelhardt <jengelh@medozas.de> netfilter: xtables: slightly better error reporting
When extended status codes are available, such as ENOMEM on failed
allocations, or subsequent functions (e.g. nf_ct_get_l3proto), passing
them up to userspace seems like a good idea compared to just always
EINVAL.
Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
|
| H A D | xt_rateest.c | 4a5a5c73 Fri Mar 19 11:32:59 CDT 2010 Jan Engelhardt <jengelh@medozas.de> netfilter: xtables: slightly better error reporting
When extended status codes are available, such as ENOMEM on failed
allocations, or subsequent functions (e.g. nf_ct_get_l3proto), passing
them up to userspace seems like a good idea compared to just always
EINVAL.
Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
4a5a5c73 Fri Mar 19 11:32:59 CDT 2010 Jan Engelhardt <jengelh@medozas.de> netfilter: xtables: slightly better error reporting
When extended status codes are available, such as ENOMEM on failed
allocations, or subsequent functions (e.g. nf_ct_get_l3proto), passing
them up to userspace seems like a good idea compared to just always
EINVAL.
Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
|
| H A D | xt_cluster.c | 4a5a5c73 Fri Mar 19 11:32:59 CDT 2010 Jan Engelhardt <jengelh@medozas.de> netfilter: xtables: slightly better error reporting
When extended status codes are available, such as ENOMEM on failed
allocations, or subsequent functions (e.g. nf_ct_get_l3proto), passing
them up to userspace seems like a good idea compared to just always
EINVAL.
Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
4a5a5c73 Fri Mar 19 11:32:59 CDT 2010 Jan Engelhardt <jengelh@medozas.de> netfilter: xtables: slightly better error reporting
When extended status codes are available, such as ENOMEM on failed
allocations, or subsequent functions (e.g. nf_ct_get_l3proto), passing
them up to userspace seems like a good idea compared to just always
EINVAL.
Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
|
| H A D | xt_CONNSECMARK.c | 4a5a5c73 Fri Mar 19 11:32:59 CDT 2010 Jan Engelhardt <jengelh@medozas.de> netfilter: xtables: slightly better error reporting
When extended status codes are available, such as ENOMEM on failed
allocations, or subsequent functions (e.g. nf_ct_get_l3proto), passing
them up to userspace seems like a good idea compared to just always
EINVAL.
Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
4a5a5c73 Fri Mar 19 11:32:59 CDT 2010 Jan Engelhardt <jengelh@medozas.de> netfilter: xtables: slightly better error reporting
When extended status codes are available, such as ENOMEM on failed
allocations, or subsequent functions (e.g. nf_ct_get_l3proto), passing
them up to userspace seems like a good idea compared to just always
EINVAL.
Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
|
| H A D | xt_time.c | 4a5a5c73 Fri Mar 19 11:32:59 CDT 2010 Jan Engelhardt <jengelh@medozas.de> netfilter: xtables: slightly better error reporting
When extended status codes are available, such as ENOMEM on failed
allocations, or subsequent functions (e.g. nf_ct_get_l3proto), passing
them up to userspace seems like a good idea compared to just always
EINVAL.
Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
4a5a5c73 Fri Mar 19 11:32:59 CDT 2010 Jan Engelhardt <jengelh@medozas.de> netfilter: xtables: slightly better error reporting
When extended status codes are available, such as ENOMEM on failed
allocations, or subsequent functions (e.g. nf_ct_get_l3proto), passing
them up to userspace seems like a good idea compared to just always
EINVAL.
Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
|
| H A D | xt_quota.c | 4a5a5c73 Fri Mar 19 11:32:59 CDT 2010 Jan Engelhardt <jengelh@medozas.de> netfilter: xtables: slightly better error reporting
When extended status codes are available, such as ENOMEM on failed
allocations, or subsequent functions (e.g. nf_ct_get_l3proto), passing
them up to userspace seems like a good idea compared to just always
EINVAL.
Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
4a5a5c73 Fri Mar 19 11:32:59 CDT 2010 Jan Engelhardt <jengelh@medozas.de> netfilter: xtables: slightly better error reporting
When extended status codes are available, such as ENOMEM on failed
allocations, or subsequent functions (e.g. nf_ct_get_l3proto), passing
them up to userspace seems like a good idea compared to just always
EINVAL.
Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
|
| H A D | xt_helper.c | 4a5a5c73 Fri Mar 19 11:32:59 CDT 2010 Jan Engelhardt <jengelh@medozas.de> netfilter: xtables: slightly better error reporting
When extended status codes are available, such as ENOMEM on failed
allocations, or subsequent functions (e.g. nf_ct_get_l3proto), passing
them up to userspace seems like a good idea compared to just always
EINVAL.
Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
4a5a5c73 Fri Mar 19 11:32:59 CDT 2010 Jan Engelhardt <jengelh@medozas.de> netfilter: xtables: slightly better error reporting
When extended status codes are available, such as ENOMEM on failed
allocations, or subsequent functions (e.g. nf_ct_get_l3proto), passing
them up to userspace seems like a good idea compared to just always
EINVAL.
Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
|
| H A D | xt_state.c | 4a5a5c73 Fri Mar 19 11:32:59 CDT 2010 Jan Engelhardt <jengelh@medozas.de> netfilter: xtables: slightly better error reporting
When extended status codes are available, such as ENOMEM on failed
allocations, or subsequent functions (e.g. nf_ct_get_l3proto), passing
them up to userspace seems like a good idea compared to just always
EINVAL.
Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
4a5a5c73 Fri Mar 19 11:32:59 CDT 2010 Jan Engelhardt <jengelh@medozas.de> netfilter: xtables: slightly better error reporting
When extended status codes are available, such as ENOMEM on failed
allocations, or subsequent functions (e.g. nf_ct_get_l3proto), passing
them up to userspace seems like a good idea compared to just always
EINVAL.
Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
|
| H A D | xt_limit.c | 4a5a5c73 Fri Mar 19 11:32:59 CDT 2010 Jan Engelhardt <jengelh@medozas.de> netfilter: xtables: slightly better error reporting
When extended status codes are available, such as ENOMEM on failed
allocations, or subsequent functions (e.g. nf_ct_get_l3proto), passing
them up to userspace seems like a good idea compared to just always
EINVAL.
Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
4a5a5c73 Fri Mar 19 11:32:59 CDT 2010 Jan Engelhardt <jengelh@medozas.de> netfilter: xtables: slightly better error reporting
When extended status codes are available, such as ENOMEM on failed
allocations, or subsequent functions (e.g. nf_ct_get_l3proto), passing
them up to userspace seems like a good idea compared to just always
EINVAL.
Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
|
| H A D | xt_NFQUEUE.c | 4a5a5c73 Fri Mar 19 11:32:59 CDT 2010 Jan Engelhardt <jengelh@medozas.de> netfilter: xtables: slightly better error reporting
When extended status codes are available, such as ENOMEM on failed
allocations, or subsequent functions (e.g. nf_ct_get_l3proto), passing
them up to userspace seems like a good idea compared to just always
EINVAL.
Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
4a5a5c73 Fri Mar 19 11:32:59 CDT 2010 Jan Engelhardt <jengelh@medozas.de> netfilter: xtables: slightly better error reporting
When extended status codes are available, such as ENOMEM on failed
allocations, or subsequent functions (e.g. nf_ct_get_l3proto), passing
them up to userspace seems like a good idea compared to just always
EINVAL.
Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
|
| H A D | xt_string.c | 4a5a5c73 Fri Mar 19 11:32:59 CDT 2010 Jan Engelhardt <jengelh@medozas.de> netfilter: xtables: slightly better error reporting
When extended status codes are available, such as ENOMEM on failed
allocations, or subsequent functions (e.g. nf_ct_get_l3proto), passing
them up to userspace seems like a good idea compared to just always
EINVAL.
Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
4a5a5c73 Fri Mar 19 11:32:59 CDT 2010 Jan Engelhardt <jengelh@medozas.de> netfilter: xtables: slightly better error reporting
When extended status codes are available, such as ENOMEM on failed
allocations, or subsequent functions (e.g. nf_ct_get_l3proto), passing
them up to userspace seems like a good idea compared to just always
EINVAL.
Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
|
| H A D | xt_connbytes.c | 4a5a5c73 Fri Mar 19 11:32:59 CDT 2010 Jan Engelhardt <jengelh@medozas.de> netfilter: xtables: slightly better error reporting
When extended status codes are available, such as ENOMEM on failed
allocations, or subsequent functions (e.g. nf_ct_get_l3proto), passing
them up to userspace seems like a good idea compared to just always
EINVAL.
Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
4a5a5c73 Fri Mar 19 11:32:59 CDT 2010 Jan Engelhardt <jengelh@medozas.de> netfilter: xtables: slightly better error reporting
When extended status codes are available, such as ENOMEM on failed
allocations, or subsequent functions (e.g. nf_ct_get_l3proto), passing
them up to userspace seems like a good idea compared to just always
EINVAL.
Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
|
| H A D | xt_connmark.c | 4a5a5c73 Fri Mar 19 11:32:59 CDT 2010 Jan Engelhardt <jengelh@medozas.de> netfilter: xtables: slightly better error reporting
When extended status codes are available, such as ENOMEM on failed
allocations, or subsequent functions (e.g. nf_ct_get_l3proto), passing
them up to userspace seems like a good idea compared to just always
EINVAL.
Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
4a5a5c73 Fri Mar 19 11:32:59 CDT 2010 Jan Engelhardt <jengelh@medozas.de> netfilter: xtables: slightly better error reporting
When extended status codes are available, such as ENOMEM on failed
allocations, or subsequent functions (e.g. nf_ct_get_l3proto), passing
them up to userspace seems like a good idea compared to just always
EINVAL.
Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
|
| H A D | xt_RATEEST.c | 4a5a5c73 Fri Mar 19 11:32:59 CDT 2010 Jan Engelhardt <jengelh@medozas.de> netfilter: xtables: slightly better error reporting
When extended status codes are available, such as ENOMEM on failed
allocations, or subsequent functions (e.g. nf_ct_get_l3proto), passing
them up to userspace seems like a good idea compared to just always
EINVAL.
Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
4a5a5c73 Fri Mar 19 11:32:59 CDT 2010 Jan Engelhardt <jengelh@medozas.de> netfilter: xtables: slightly better error reporting
When extended status codes are available, such as ENOMEM on failed
allocations, or subsequent functions (e.g. nf_ct_get_l3proto), passing
them up to userspace seems like a good idea compared to just always
EINVAL.
Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
|
| H A D | xt_LED.c | 4a5a5c73 Fri Mar 19 11:32:59 CDT 2010 Jan Engelhardt <jengelh@medozas.de> netfilter: xtables: slightly better error reporting
When extended status codes are available, such as ENOMEM on failed
allocations, or subsequent functions (e.g. nf_ct_get_l3proto), passing
them up to userspace seems like a good idea compared to just always
EINVAL.
Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
4a5a5c73 Fri Mar 19 11:32:59 CDT 2010 Jan Engelhardt <jengelh@medozas.de> netfilter: xtables: slightly better error reporting
When extended status codes are available, such as ENOMEM on failed
allocations, or subsequent functions (e.g. nf_ct_get_l3proto), passing
them up to userspace seems like a good idea compared to just always
EINVAL.
Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
|
| H A D | xt_conntrack.c | 4a5a5c73 Fri Mar 19 11:32:59 CDT 2010 Jan Engelhardt <jengelh@medozas.de> netfilter: xtables: slightly better error reporting
When extended status codes are available, such as ENOMEM on failed
allocations, or subsequent functions (e.g. nf_ct_get_l3proto), passing
them up to userspace seems like a good idea compared to just always
EINVAL.
Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
4a5a5c73 Fri Mar 19 11:32:59 CDT 2010 Jan Engelhardt <jengelh@medozas.de> netfilter: xtables: slightly better error reporting
When extended status codes are available, such as ENOMEM on failed
allocations, or subsequent functions (e.g. nf_ct_get_l3proto), passing
them up to userspace seems like a good idea compared to just always
EINVAL.
Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
|
| H A D | xt_connlimit.c | 4a5a5c73 Fri Mar 19 11:32:59 CDT 2010 Jan Engelhardt <jengelh@medozas.de> netfilter: xtables: slightly better error reporting
When extended status codes are available, such as ENOMEM on failed
allocations, or subsequent functions (e.g. nf_ct_get_l3proto), passing
them up to userspace seems like a good idea compared to just always
EINVAL.
Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
4a5a5c73 Fri Mar 19 11:32:59 CDT 2010 Jan Engelhardt <jengelh@medozas.de> netfilter: xtables: slightly better error reporting
When extended status codes are available, such as ENOMEM on failed
allocations, or subsequent functions (e.g. nf_ct_get_l3proto), passing
them up to userspace seems like a good idea compared to just always
EINVAL.
Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
|
| H A D | xt_CT.c | 4a5a5c73 Fri Mar 19 11:32:59 CDT 2010 Jan Engelhardt <jengelh@medozas.de> netfilter: xtables: slightly better error reporting
When extended status codes are available, such as ENOMEM on failed
allocations, or subsequent functions (e.g. nf_ct_get_l3proto), passing
them up to userspace seems like a good idea compared to just always
EINVAL.
Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
4a5a5c73 Fri Mar 19 11:32:59 CDT 2010 Jan Engelhardt <jengelh@medozas.de> netfilter: xtables: slightly better error reporting
When extended status codes are available, such as ENOMEM on failed
allocations, or subsequent functions (e.g. nf_ct_get_l3proto), passing
them up to userspace seems like a good idea compared to just always
EINVAL.
Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
|
| H A D | xt_recent.c | 4a5a5c73 Fri Mar 19 11:32:59 CDT 2010 Jan Engelhardt <jengelh@medozas.de> netfilter: xtables: slightly better error reporting
When extended status codes are available, such as ENOMEM on failed
allocations, or subsequent functions (e.g. nf_ct_get_l3proto), passing
them up to userspace seems like a good idea compared to just always
EINVAL.
Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
4a5a5c73 Fri Mar 19 11:32:59 CDT 2010 Jan Engelhardt <jengelh@medozas.de> netfilter: xtables: slightly better error reporting
When extended status codes are available, such as ENOMEM on failed
allocations, or subsequent functions (e.g. nf_ct_get_l3proto), passing
them up to userspace seems like a good idea compared to just always
EINVAL.
Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
|
| H A D | xt_hashlimit.c | 4a5a5c73 Fri Mar 19 11:32:59 CDT 2010 Jan Engelhardt <jengelh@medozas.de> netfilter: xtables: slightly better error reporting
When extended status codes are available, such as ENOMEM on failed
allocations, or subsequent functions (e.g. nf_ct_get_l3proto), passing
them up to userspace seems like a good idea compared to just always
EINVAL.
Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
4a5a5c73 Fri Mar 19 11:32:59 CDT 2010 Jan Engelhardt <jengelh@medozas.de> netfilter: xtables: slightly better error reporting
When extended status codes are available, such as ENOMEM on failed
allocations, or subsequent functions (e.g. nf_ct_get_l3proto), passing
them up to userspace seems like a good idea compared to just always
EINVAL.
Signed-off-by: Jan Engelhardt <jengelh@medozas.de>
|