All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: Florian Westphal <fw@strlen.de>, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] netfilter: ipset: hash:net,iface: fix interface comparision
Date: Tue, 26 Jun 2012 15:35:01 +0200	[thread overview]
Message-ID: <20120626133501.GA8050@1984> (raw)
In-Reply-To: <alpine.DEB.2.00.1206260904520.8075@blackhole.kfki.hu>

On Tue, Jun 26, 2012 at 09:08:31AM +0200, Jozsef Kadlecsik wrote:
> On Mon, 25 Jun 2012, Pablo Neira Ayuso wrote:
> 
> > On Sun, Jun 17, 2012 at 09:56:46PM +0200, Florian Westphal wrote:
> > > ifname_compare() assumes that skb->dev is zero-padded,
> > > e.g 'eth1\0\0\0\0\0...'. This isn't always the case. e1000 driver does
> > > 
> > > strncpy(netdev->name, pci_name(pdev), sizeof(netdev->name) - 1);
> > > 
> > > in e1000_probe(), so once device is registered dev->name memory contains
> > > 'eth1\0:0:3\0\0\0' (or something like that), which makes eth1 compare
> > > fail.
> > > 
> > > Use plain strcmp() instead.
> > 
> > Applied, thanks Florian.
> 
> Thanks, Pablo! I had commited the patch in my ipset git tree, just haven't 
> time yet to send/ack to you.

No problem. Please, rebase your tree to remove it:

git rebase -i COMMIT_YOU_WANT_TO_REMOVE^
# then, write "e" in the patch you want to remove on the list that it shows
git reset HEAD^
git reset --hard
git rebase --continue

Not sure if there's a smarter way to do it. This is how I make it
though.

Note that we're on -rc4, so please send me important fixes that you
want me to pass to David first, after that those to net-next.

Thanks Jozsef.

      reply	other threads:[~2012-06-26 13:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-17 19:56 [PATCH] netfilter: ipset: hash:net,iface: fix interface comparision Florian Westphal
2012-06-25 13:11 ` Pablo Neira Ayuso
2012-06-26  7:08   ` Jozsef Kadlecsik
2012-06-26 13:35     ` Pablo Neira Ayuso [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=20120626133501.GA8050@1984 \
    --to=pablo@netfilter.org \
    --cc=fw@strlen.de \
    --cc=kadlec@blackhole.kfki.hu \
    --cc=netfilter-devel@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 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.