From: Jeff Garzik <jgarzik@pobox.com>
To: Jay Vosburgh <fubar@us.ibm.com>
Cc: netdev@vger.kernel.org, bonding-devel@lists.sourceforge.net
Subject: Re: [PATCH 1/3] bonding: fix double dev_add_pack
Date: Tue, 06 Mar 2007 06:10:12 -0500 [thread overview]
Message-ID: <45ED4C14.2020301@pobox.com> (raw)
In-Reply-To: <200703010103.l2113K22030733@death.nxdomain.ibm.com>
Jay Vosburgh wrote:
> Bonding can erroneously register the same packet_type to receive
> ARPs (for use by ARP validation): once at device open time, and once via
> sysfs. Since sysfs can change the validate setting (and thus register
> or unregister) at any time, a flag is needed to synchronize with device
> open in order to avoid double registrations, and the simplest place is
> within the packet_type structure itself. Double unregister is not an
> issue.
>
> Bug reported by Ulrich Oelmann <ulrich.oelmann@web.de>.
>
> Signed-off-by: Jay Vosburgh <fubar@us.ibm.com>
applied 1-3
prev parent reply other threads:[~2007-03-06 11:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-01 1:03 [PATCH 1/3] bonding: fix double dev_add_pack Jay Vosburgh
2007-03-06 11:10 ` Jeff Garzik [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=45ED4C14.2020301@pobox.com \
--to=jgarzik@pobox.com \
--cc=bonding-devel@lists.sourceforge.net \
--cc=fubar@us.ibm.com \
--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;
as well as URLs for NNTP newsgroup(s).