netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: netfilter-devel@vger.kernel.org
Cc: rgb@redhat.com, paul@paul-moore.com
Subject: Re: [PATCH nf-next] netfilter: nf_tables: rise cap on SELinux secmark context
Date: Wed, 26 Jun 2024 13:31:40 +0200	[thread overview]
Message-ID: <Znv8HMKbgSCwdPp-@calendula> (raw)
In-Reply-To: <20240603181659.5998-1-pablo@netfilter.org>

Enqueued to nf-next to address:

https://bugzilla.netfilter.org/show_bug.cgi?id=1749

On Mon, Jun 03, 2024 at 08:16:59PM +0200, Pablo Neira Ayuso wrote:
> secmark context is artificially limited 256 bytes, rise it to 4Kbytes.
> 
> Fixes: fb961945457f ("netfilter: nf_tables: add SECMARK support")
> Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
> ---
>  include/uapi/linux/netfilter/nf_tables.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/include/uapi/linux/netfilter/nf_tables.h b/include/uapi/linux/netfilter/nf_tables.h
> index aa4094ca2444..639894ed1b97 100644
> --- a/include/uapi/linux/netfilter/nf_tables.h
> +++ b/include/uapi/linux/netfilter/nf_tables.h
> @@ -1376,7 +1376,7 @@ enum nft_secmark_attributes {
>  #define NFTA_SECMARK_MAX	(__NFTA_SECMARK_MAX - 1)
>  
>  /* Max security context length */
> -#define NFT_SECMARK_CTX_MAXLEN		256
> +#define NFT_SECMARK_CTX_MAXLEN		4096
>  
>  /**
>   * enum nft_reject_types - nf_tables reject expression reject types
> -- 
> 2.30.2
> 
> 

  reply	other threads:[~2024-06-26 11:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-03 18:16 [PATCH nf-next] netfilter: nf_tables: rise cap on SELinux secmark context Pablo Neira Ayuso
2024-06-26 11:31 ` Pablo Neira Ayuso [this message]
2024-06-26 15:45   ` Paul Moore

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Znv8HMKbgSCwdPp-@calendula \
    --to=pablo@netfilter.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=paul@paul-moore.com \
    --cc=rgb@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).