From: David Miller <davem@davemloft.net>
To: jakub.kicinski@netronome.com
Cc: netdev@vger.kernel.org, oss-drivers@netronome.com,
alexei.starovoitov@gmail.com
Subject: Re: [PATCH net v2 0/2] net/tls: redo the RX resync locking
Date: Tue, 04 Jun 2019 13:55:25 -0700 (PDT) [thread overview]
Message-ID: <20190604.135525.221064103005473136.davem@davemloft.net> (raw)
In-Reply-To: <20190604190012.6327-1-jakub.kicinski@netronome.com>
From: Jakub Kicinski <jakub.kicinski@netronome.com>
Date: Tue, 4 Jun 2019 12:00:10 -0700
> Hi!
>
> Take two of making sure we don't use a NULL netdev pointer
> for RX resync. This time using a bit and an open coded
> wait loop.
>
> v2:
> - fix build warning (DaveM).
:-) Applied and queued up for -stable.
prev parent reply other threads:[~2019-06-04 20:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 19:00 [PATCH net v2 0/2] net/tls: redo the RX resync locking Jakub Kicinski
2019-06-04 19:00 ` [PATCH net v2 1/2] Revert "net/tls: avoid NULL-deref on resync during device removal" Jakub Kicinski
2019-06-04 19:00 ` [PATCH net v2 2/2] net/tls: replace the sleeping lock around RX resync with a bit lock Jakub Kicinski
2019-06-04 20:55 ` David Miller [this message]
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=20190604.135525.221064103005473136.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alexei.starovoitov@gmail.com \
--cc=jakub.kicinski@netronome.com \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.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).