All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikolai Zhubr <n-a-zhubr@yandex.ru>
To: Eric Blake <eblake@redhat.com>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
	libvirt-users@redhat.com, netfilter@vger.kernel.org
Subject: Re: [libvirt-users] netfilter+libvirt=(smth got broken?)
Date: Thu, 21 Mar 2013 14:32:17 +0400	[thread overview]
Message-ID: <514AE1B1.4050203@yandex.ru> (raw)
In-Reply-To: <514A7BFD.5060401@redhat.com>

Hello all,
21.03.2013 7:18, Eric Blake:
[...]
>> --ctdir was broken and it was fixed in patch:
>
> In other words, the kernel folks made a silent change in ABI.  Eww.
>
> How can we reliably tell which kernels have the old behavior, and which
> have the new, so that libvirt knows which sense to use?

There are so many customized kernels in the wild with whatever mix of 
patches applied and whatever custom versioning involved that IMHO no one 
can now really know without some special flag added for that (other than 
try and see)

[...]
>> It's unfortunate nobody noticed this rule was incorrect so far (even
>> if it was working).

In this case I'd say it was rather just somewhat inconsistent with it 
own documentation. Not a big deal. IMHO it would be OK to just add a 
notice to documentation saying that "for historical reasons" behaviour 
is inverted, instead of changing the code in question to make it wrose.

Alternatively, upon noticing unwanted inversion, netfilter could just 
introduce some new correct --ctdir2 and subsequently depreciate and 
remove original --ctdir, allowing some time for adaptation.

>
> It's also unfortunate that the kernel folks did a silent ABI change,
> without offering any witness of which behavior is in operation.
>

Yes, netfilter is extremely valuable and extremely respected project. 
However, breaking the work of other people so easily, for almost no 
reason, without even a word of discussion and without any proposed way 
to relaibly handle the situation seems surprising at least. Huge number 
of people depend on netfilter, really! Sorry for some rant.


Nikolai

      parent reply	other threads:[~2013-03-21 10:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-20 12:47 netfilter+libvirt=(smth got broken?) Nikolai Zhubr
2013-03-20 13:06 ` Nikolai Zhubr
2013-03-20 13:41 ` Nikolai Zhubr
     [not found]   ` <514A1F0A.4090402@laine.org>
     [not found]     ` <514A1F0A.4090402-k/Ak44NBdeXYtjvyW6yDsg@public.gmane.org>
2013-03-20 23:01       ` Nikolai Zhubr
2013-03-21  2:30   ` Pablo Neira Ayuso
2013-03-21  3:18     ` [libvirt-users] " Eric Blake
2013-03-21  9:55       ` Pablo Neira Ayuso
2013-03-22 10:53         ` Pablo Neira Ayuso
2013-03-22 18:10           ` Laine Stump
2013-03-26 14:18             ` Pablo Neira Ayuso
2013-03-27 18:22               ` Laine Stump
2013-03-21 10:32       ` Nikolai Zhubr [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=514AE1B1.4050203@yandex.ru \
    --to=n-a-zhubr@yandex.ru \
    --cc=eblake@redhat.com \
    --cc=libvirt-users@redhat.com \
    --cc=netfilter@vger.kernel.org \
    --cc=pablo@netfilter.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.