linux-kernel - Re: [PATCH 16/19] staging: lustre: use explicit poll loop in ptlrpc_unregister

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LFD.2.21.1801171535280.11282@casper.infradead.org>
Date:   Wed, 17 Jan 2018 15:35:39 +0000 (GMT)
From:   James Simmons <jsimmons@...radead.org>
To:     NeilBrown <neilb@...e.com>
cc:     Oleg Drokin <oleg.drokin@...el.com>,
        Andreas Dilger <andreas.dilger@...el.com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        lkml <linux-kernel@...r.kernel.org>,
        lustre <lustre-devel@...ts.lustre.org>
Subject: Re: [PATCH 16/19] staging: lustre: use explicit poll loop in
 ptlrpc_unregister_reply


> replace l_wait_event() with wait_event_idle_timeout() and explicit
> loop.  This approach is easier to understand.

Reviewed-by: James Simmons <jsimmons@...radead.org>
 
> Signed-off-by: NeilBrown <neilb@...e.com>
> ---
>  drivers/staging/lustre/lustre/ptlrpc/client.c |   14 +++++++-------
>  1 file changed, 7 insertions(+), 7 deletions(-)
> 
> diff --git a/drivers/staging/lustre/lustre/ptlrpc/client.c b/drivers/staging/lustre/lustre/ptlrpc/client.c
> index f70176c6db08..ffdd3ffd62c6 100644
> --- a/drivers/staging/lustre/lustre/ptlrpc/client.c
> +++ b/drivers/staging/lustre/lustre/ptlrpc/client.c
> @@ -2500,7 +2500,6 @@ static int ptlrpc_unregister_reply(struct ptlrpc_request *request, int async)
>  {
>  	int rc;
>  	wait_queue_head_t *wq;
> -	struct l_wait_info lwi;
>  
>  	/* Might sleep. */
>  	LASSERT(!in_interrupt());
> @@ -2543,16 +2542,17 @@ static int ptlrpc_unregister_reply(struct ptlrpc_request *request, int async)
>  		 * Network access will complete in finite time but the HUGE
>  		 * timeout lets us CWARN for visibility of sluggish NALs
>  		 */
> -		lwi = LWI_TIMEOUT_INTERVAL(LONG_UNLINK * HZ,
> -					   HZ, NULL, NULL);
> -		rc = l_wait_event(*wq, !ptlrpc_client_recv_or_unlink(request),
> -				  &lwi);
> -		if (rc == 0) {
> +		int cnt = 0;
> +		while (cnt < LONG_UNLINK &&
> +		       (rc = wait_event_idle_timeout(*wq,
> +						     !ptlrpc_client_recv_or_unlink(request),
> +						     HZ)) == 0)
> +			cnt += 1;
> +		if (rc > 0) {
>  			ptlrpc_rqphase_move(request, request->rq_next_phase);
>  			return 1;
>  		}
>  
> -		LASSERT(rc == -ETIMEDOUT);
>  		DEBUG_REQ(D_WARNING, request,
>  			  "Unexpectedly long timeout receiving_reply=%d req_ulinked=%d reply_unlinked=%d",
>  			  request->rq_receiving_reply,
> 
> 
>