From: David Howells <dhowells@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: dhowells@redhat.com, linux-afs@lists.infradead.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] rxrpc: Don't permit use of connect() op and simplify sendmsg() op
Date: Fri, 15 Apr 2016 04:26:10 +0100 [thread overview]
Message-ID: <4962.1460690770@warthog.procyon.org.uk> (raw)
In-Reply-To: <20160414.210713.1128991767536792390.davem@davemloft.net>
David Miller <davem@davemloft.net> wrote:
> > Simplify the RxRPC user interface and remove the use of connect() to direct
> > client calls. It is redundant given that sendmsg() can be given the target
> > address and calls to multiple targets are permitted from a client socket
> > and also from a service socket.
>
> You can't just change completely the socket semantics for your
> protocol like this, every single userland application is going to
> break.
>
> Sorry, there is no way I am applying changes like this.
Okay, fair enough.[*]
David
[*] I could point out that there is only one (under construction) userspace
application that uses this - and that doesn't use connect - but I can't quite
be 100% sure of that, so your point stands.
next prev parent reply other threads:[~2016-04-15 3:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-12 15:05 [PATCH 0/3] RxRPC: 2nd rewrite part 2 David Howells
2016-04-12 15:05 ` [PATCH 1/3] rxrpc: Don't permit use of connect() op and simplify sendmsg() op David Howells
2016-04-15 1:07 ` David Miller
2016-04-15 3:26 ` David Howells [this message]
2016-04-12 15:05 ` [PATCH 2/3] rxrpc: The RXRPC_ACCEPT control message should not have an address David Howells
2016-04-12 15:05 ` [PATCH 3/3] rxrpc: Use the listen() system call to move to listening state David Howells
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=4962.1460690770@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=davem@davemloft.net \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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