From: David Miller <davem@davemloft.net>
To: tv@lio96.de
Cc: netdev@vger.kernel.org
Subject: Re: PF_NETLINK, SOCK_DGRAM, 2 => EPROTONOSUPPORT
Date: Tue, 31 Aug 2010 09:50:04 -0700 (PDT) [thread overview]
Message-ID: <20100831.095004.173857635.davem@davemloft.net> (raw)
In-Reply-To: <alpine.LNX.2.00.1008311213300.3405@er-systems.de>
From: Thomas Voegtle <tv@lio96.de>
Date: Tue, 31 Aug 2010 12:15:26 +0200 (CEST)
> On Mon, 30 Aug 2010, David Miller wrote:
>
>> From: Thomas Voegtle <tv@lio96.de>
>> Date: Mon, 30 Aug 2010 12:02:51 +0200 (CEST)
>>
>>> Was this intended, that this code snippet doesn't work this way
>>> anymore or is this just a bug?
>>
>> It's an unintended regression.
>>
>> But nobody noticed it, because almost no-one uses NETLINK_USER.
>>
>> This might fix it, give it a test:
>
>
> Yes, that fixes it. Tested with 2.6.35.4 and 2.6.36-rc3.
Thanks for testing.
prev parent reply other threads:[~2010-08-31 16:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-30 10:02 PF_NETLINK, SOCK_DGRAM, 2 => EPROTONOSUPPORT Thomas Voegtle
2010-08-31 2:06 ` David Miller
2010-08-31 10:15 ` Thomas Voegtle
2010-08-31 16:50 ` 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=20100831.095004.173857635.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=tv@lio96.de \
/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).