All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergei Trofimovich <slyfox@gentoo.org>
To: Soheil Hassas Yeganeh <soheil@google.com>,
	"Signed-off-by: David S. Miller" <davem@davemloft.net>,
	netdev@vger.kernel.org
Cc: Willem de Bruijn <willemb@google.com>, Tanu Kaskinen <tanuk@iki.fi>
Subject: [BUG?] tcp regression in v4.7-r1: c14ac9451c34832554db33386a4393be8bba3a7b breaks pulseaudio over TCP
Date: Sun, 10 Jul 2016 12:42:40 +0100	[thread overview]
Message-ID: <20160710124240.7d484f44@sf> (raw)

[-- Attachment #1: Type: text/plain, Size: 1039 bytes --]

Hi netdev folk!

Commit c14ac9451c34832554db33386a4393be8bba3a7b
broke pulseaudio (PA) over TCP.

PA does unusual thing: it calls
    sendmsg(cmsg_type=SCM_CREDENTIALS)
on a TCP socket. It's not a new PA behaviour though.

Originally reported as PA bug (has more details)
    https://bugs.freedesktop.org/show_bug.cgi?id=96873

It looks like kernel used to ignore control messages
but now it does not:
    http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/diff/net/ipv4/tcp.c?id=c14ac9451c34832554db33386a4393be8bba3a7b

+	if (msg->msg_controllen) {
+		err = sock_cmsg_send(sk, msg, &sockc);
+		if (unlikely(err)) {
+			err = -EINVAL;
+			goto out_err;
+		}
+	}

This change breaks streaming of pulse clients.

Pulseaudio will be fixed at some point.

But kernel change does not look like intentional
breakage of old behaviour.

Perhaps kernel should have a grace period and only
warn about unsupported control messages for a socket?

Last working kernel: v4.6

Thanks!

-- 

  Sergei

[-- Attachment #2: Цифровая подпись OpenPGP --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

             reply	other threads:[~2016-07-10 11:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-10 11:42 Sergei Trofimovich [this message]
2016-07-10 15:15 ` [BUG?] tcp regression in v4.7-r1: c14ac9451c34832554db33386a4393be8bba3a7b breaks pulseaudio over TCP Soheil Hassas Yeganeh
2016-07-10 16:25   ` Sergei Trofimovich
2016-07-10 16:32     ` Soheil Hassas Yeganeh

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=20160710124240.7d484f44@sf \
    --to=slyfox@gentoo.org \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=soheil@google.com \
    --cc=tanuk@iki.fi \
    --cc=willemb@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.