From: Dan Williams <dcbw@redhat.com>
To: Thomas Graf <tgraf@suug.ch>
Cc: "Denis V. Lunev" <den@sw.ru>,
netdev@vger.kernel.org, "Denis V. Lunev" <den@openvz.org>,
"David S. Miller" <davem@davemloft.net>,
Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>
Subject: Re: Regression in current git - Network Manager fails (bisected)
Date: Tue, 23 Oct 2007 10:10:18 -0400 [thread overview]
Message-ID: <1193148618.8648.22.camel@localhost.localdomain> (raw)
In-Reply-To: <20071023133823.GB8125@postel.suug.ch>
On Tue, 2007-10-23 at 15:38 +0200, Thomas Graf wrote:
> * Denis V. Lunev <den@sw.ru> 2007-10-23 17:09
> > I have reproduced the problem with one-line test.
> > ./nl-route-get 192.168.1.1
> > The problem is with this message:
> >
> > -- Debug: Sent Message:
> > -------------------------- BEGIN NETLINK MESSAGE
> > ---------------------------
> > [HEADER] 16 octets
> > .nlmsg_len = 20
> > .nlmsg_type = 18 <route/link>
> > .nlmsg_flags = 773 <REQUEST,ACK,ROOT,MATCH>
> > .nlmsg_seq = 1193143772
> > .nlmsg_pid = 8233
> > [PAYLOAD] 16 octets
> > 00 1d fa 20 00 00 00 00 81 0e 02 00 00 00 00 00 ... ............
> > --------------------------- END NETLINK MESSAGE
> > ---------------------------
> > it starts dump and requests ACK.
>
> libnl sets the ACK bit for all requests unless the application
> disables this behaviour.
Should I make NM disable ACKs for now until it gets fixed?
Dan
next prev parent reply other threads:[~2007-10-23 14:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-22 0:58 Regression in current git - Network Manager fails (bisected) Joseph Fannin
2007-10-22 9:22 ` Denis V. Lunev
2007-10-22 15:57 ` Dan Williams
2007-10-23 12:11 ` Thomas Graf
2007-10-23 13:09 ` Denis V. Lunev
2007-10-23 13:38 ` Thomas Graf
2007-10-23 14:10 ` Dan Williams [this message]
2007-10-25 9:06 ` Thomas Graf
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=1193148618.8648.22.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=davem@davemloft.net \
--cc=den@openvz.org \
--cc=den@sw.ru \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@vger.kernel.org \
--cc=tgraf@suug.ch \
/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.