linux-kernel - Re: [PATCH net 0/6] rxrpc: Fixes

lists.openwall.net		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 linux-cve-announce 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]

Message-Id: <20190412.165813.1409453216111845470.davem@davemloft.net>
Date:   Fri, 12 Apr 2019 16:58:13 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     dhowells@...hat.com
Cc:     netdev@...r.kernel.org, linux-afs@...ts.infradead.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH net 0/6] rxrpc: Fixes

From: David Howells <dhowells@...hat.com>
Date: Fri, 12 Apr 2019 16:33:33 +0100

> Here is a collection of fixes for rxrpc:
> 
>  (1) rxrpc_error_report() needs to call sock_error() to clear the error
>      code from the UDP transport socket, lest it be unexpectedly revisited
>      on the next kernel_sendmsg() call.  This has been causing all sorts of
>      weird effects in AFS as the effects have typically been felt by the
>      wrong RxRPC call.
> 
>  (2) Allow a kernel user of AF_RXRPC to easily detect if an rxrpc call has
>      completed.
> 
>  (3) Allow errors incurred by attempting to transmit data through the UDP
>      socket to get back up the stack to AFS.
> 
>  (4) Make AFS use (2) to abort the synchronous-mode call waiting loop if
>      the rxrpc-level call completed.
> 
>  (5) Add a missing tracepoint case for tracing abort reception.
> 
>  (6) Fix detection and handling of out-of-order ACKs.
> 
> For the patch series:
> 
> Tested-by: Jonathan Billings <jsbillin@...ch.edu>

Series applied, thanks.