linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: David Teigland <teigland@redhat.com>
To: Gionatan Danti <g.danti@assyoma.it>
Cc: linux-lvm@redhat.com, heming.zhao@suse.com
Subject: Re: [linux-lvm] commit c527a0cbfc3 may have a bug
Date: Fri, 14 Feb 2020 14:40:28 -0600	[thread overview]
Message-ID: <20200214204028.GB20792@redhat.com> (raw)
In-Reply-To: <1f438b012d606d06d77ff9a1fc3a6926@assyoma.it>

On Fri, Feb 14, 2020 at 08:34:19PM +0100, Gionatan Danti wrote:
> Hi David, being filters one of the most asked questions, can I ask why we
> have so many different filters, leading to such complex interactions and
> behaviors?
> 
> Don't get me wrong: I am sure you (the lvm team) have very good reasons to
> do that, and I am surely missing something? But what, precisely? How should
> we (end users) consider filters? Should we only use global_filter?

You're right, filters are difficult to understand and use correctly.  The
complexity and confusion in the code is no better.  With the removal of
lvmetad in 2.03 versions (e.g. RHEL8) there's no difference between filter
and global_filter, so that's some small improvement.  But, I think filters
should be replaced or overhauled with something easier to use and more
useful at a technical level.

I've created a bz about that and welcome thoughts about what a replacement
should or should not be like.  With input the work is more likely to be
prioritized.

https://bugzilla.redhat.com/show_bug.cgi?id=1803266

  reply	other threads:[~2020-02-14 20:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <098d6e8d-2d2c-5067-1435-eefd7e2d09bc@suse.com>
2020-02-14 15:18 ` [linux-lvm] commit c527a0cbfc3 may have a bug heming.zhao
2020-02-14 19:11 ` David Teigland
2020-02-14 19:34   ` Gionatan Danti
2020-02-14 20:40     ` David Teigland [this message]
2020-02-15  5:22       ` heming.zhao
2020-02-15 12:40       ` Zdenek Kabelac
2020-02-15 19:15         ` Gionatan Danti
2020-02-15 20:19           ` Zdenek Kabelac
2020-02-16 15:17             ` Gionatan Danti
2020-02-15 20:49           ` Chris Murphy
2020-02-16 15:28             ` Gionatan Danti
2020-02-15 19:07       ` Gionatan Danti

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=20200214204028.GB20792@redhat.com \
    --to=teigland@redhat.com \
    --cc=g.danti@assyoma.it \
    --cc=heming.zhao@suse.com \
    --cc=linux-lvm@redhat.com \
    /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).