lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Wed, 6 May 2020 08:47:25 +0200
From:   Greg KH <>
To:     ashwin-h <>
Cc:,,,,,,,,,,, Xin Long <>
Subject: Re: [PATCH 1/2] sctp: implement memory accounting on tx path

On Wed, May 06, 2020 at 07:50:53PM +0530, ashwin-h wrote:
> From: Xin Long <>
> commit 1033990ac5b2ab6cee93734cb6d301aa3a35bcaa upstream.
> Now when sending packets, sk_mem_charge() and sk_mem_uncharge() have been
> used to set sk_forward_alloc. We just need to call sk_wmem_schedule() to
> check if the allocated should be raised, and call sk_mem_reclaim() to
> check if the allocated should be reduced when it's under memory pressure.
> If sk_wmem_schedule() returns false, which means no memory is allowed to
> allocate, it will block and wait for memory to become available.
> Note different from tcp, sctp wait_for_buf happens before allocating any
> skb, so memory accounting check is done with the whole msg_len before it
> too.
> Reported-by: Matteo Croce <>
> Tested-by: Matteo Croce <>
> Acked-by: Neil Horman <>
> Acked-by: Marcelo Ricardo Leitner <>
> Signed-off-by: Xin Long <>
> Signed-off-by: David S. Miller <>
> Signed-off-by: Ashwin H <>
> ---
>  net/sctp/socket.c | 10 ++++++++--
>  1 file changed, 8 insertions(+), 2 deletions(-)


This is not the correct way to submit patches for inclusion in the
stable kernel tree.  Please read:
for how to do this properly.


Powered by blists - more mailing lists