From: David Miller <davem@davemloft.net>
To: torvalds@linux-foundation.org
Cc: rjw@sisk.pl, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org, netdev@vger.kernel.org,
kaber@trash.net, jengelh@medozas.de
Subject: Re: 2.6.35-rc4-git3: Reported regressions from 2.6.34
Date: Thu, 08 Jul 2010 21:34:20 -0700 (PDT) [thread overview]
Message-ID: <20100708.213420.112614033.davem@davemloft.net> (raw)
In-Reply-To: <AANLkTiknnzWyVpqnPCpyiEVHLgkewd0zaGzLInABRe2G@mail.gmail.com>
From: Linus Torvalds <torvalds@linux-foundation.org>
Date: Thu, 8 Jul 2010 18:34:25 -0700
> On Thu, Jul 8, 2010 at 4:33 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
>>
>> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16187
>> Subject : Carrier detection failed in dhcpcd when link is up
>> Submitter : Christian Casteyde <casteyde.christian@free.fr>
>> Date : 2010-06-12 15:15 (27 days old)
>> First-Bad-Commit: http://git.kernel.org/linus/10708f37ae729baba9b67bd134c3720709d4ae62
>> Handled-By : Andrew Morton <akpm@linux-foundation.org>
>
> David? This bisects to a networking commit. Doesn't look sensible, but
> what do I know?
My suspicion is that dhcpd uses netlink to dump the info of the
available links, and due to some bug gets confused with the new 64-bit
statistic netlink attribute being there now.
That shouldn't happen, applications should just ignore the attributes
which they don't understand.
I'll try to find a second to have a look at this.
next prev parent reply other threads:[~2010-07-09 4:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-08 23:33 2.6.35-rc4-git3: Reported regressions from 2.6.34 Rafael J. Wysocki
2010-07-09 0:16 ` Sedat Dilek
2010-07-09 0:48 ` Andrew Hendry
2010-07-09 1:34 ` Linus Torvalds
2010-07-09 2:56 ` Frederic Weisbecker
2010-07-09 3:36 ` Shawn Starr
2010-07-09 4:34 ` David Miller [this message]
2010-07-09 5:28 ` Eric Dumazet
2010-07-09 6:20 ` David Miller
[not found] ` <AANLkTiknnzWyVpqnPCpyiEVHLgkewd0zaGzLInABRe2G-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-07-09 2:04 ` Frederic Weisbecker
2010-07-09 21:35 ` Rafael J. Wysocki
2010-07-09 7:11 ` Ingo Molnar
2010-07-09 15:12 ` Jesse Barnes
2010-07-09 21:33 ` Rafael J. Wysocki
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=20100708.213420.112614033.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--cc=jengelh@medozas.de \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).