From: David Howells <dhowells@redhat.com>
To: netdev@vger.kernel.org
Cc: dhowells@redhat.com, linux-afs@lists.infradead.org,
Tim Smith <tim@electronghost.co.uk>,
Alexey Khoroshilov <khoroshilov@ispras.ru>,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] AF_RXRPC fixes
Date: Tue, 28 Jan 2014 17:07:36 +0000 [thread overview]
Message-ID: <8672.1390928856@warthog.procyon.org.uk> (raw)
Here are some small AF_RXRPC fixes.
(1) Fix a place where a spinlock is taken conditionally but is released
unconditionally.
(2) Fix a double-free that happens when cleaning up on a checksum error.
(3) Fix handling of CHECKSUM_PARTIAL whilst delivering messages to userspace.
David
---
The following changes since commit d8ec26d7f8287f5788a494f56e8814210f0e64be:
Linux 3.13 (2014-01-19 18:40:07 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git tags/rxrpc-20140126
for you to fetch changes up to 1ea427359dde1573815e19c411ce08fdf0c42cfe:
af_rxrpc: Handle frames delivered from another VM (2014-01-26 11:45:04 +0000)
----------------------------------------------------------------
RxRPC fixes
----------------------------------------------------------------
Alexey Khoroshilov (1):
RxRPC: do not unlock unheld spinlock in rxrpc_connect_exclusive()
Tim Smith (2):
af_rxrpc: Avoid setting up double-free on checksum error
af_rxrpc: Handle frames delivered from another VM
net/rxrpc/ar-connection.c | 2 ++
net/rxrpc/ar-recvmsg.c | 7 ++++++-
2 files changed, 8 insertions(+), 1 deletion(-)
next reply other threads:[~2014-01-28 17:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 17:07 David Howells [this message]
2014-01-28 20:11 ` Do you prefer git pulls or patches posting for networking stuff? David Howells
2014-01-28 20:16 ` David Miller
2014-01-29 2:05 ` [GIT PULL] AF_RXRPC fixes 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=8672.1390928856@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=khoroshilov@ispras.ru \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tim@electronghost.co.uk \
/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).