From: David Miller <davem@davemloft.net>
To: mail@timurcelik.de
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tun: fix blocking read
Date: Sun, 24 Feb 2019 22:12:36 -0800 (PST) [thread overview]
Message-ID: <20190224.221236.905722532971991928.davem@davemloft.net> (raw)
In-Reply-To: <20190223115313.15064-1-mail@timurcelik.de>
From: Timur Celik <mail@timurcelik.de>
Date: Sat, 23 Feb 2019 12:53:13 +0100
> This patch moves setting of the current state into the loop. Otherwise
> the task may end up in a busy wait loop if none of the break conditions
> are met.
>
> Signed-off-by: Timur Celik <mail@timurcelik.de>
Applied and queued up for -stable, thanks.
next prev parent reply other threads:[~2019-02-25 6:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-23 11:53 [PATCH] tun: fix blocking read Timur Celik
2019-02-25 6:12 ` David Miller [this message]
2019-02-25 15:53 ` Eric Dumazet
2019-02-25 18:25 ` David Miller
2019-02-25 20:12 ` Timur Celik
2019-02-25 20:13 ` [PATCH] tun: remove unnecessary memory barrier Timur Celik
2019-02-25 20:15 ` Eric Dumazet
2019-02-25 22:28 ` David Miller
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=20190224.221236.905722532971991928.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@timurcelik.de \
--cc=netdev@vger.kernel.org \
/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).