From: Andrew Morton <akpm@linux-foundation.org>
To: Takaya Saeki <takayas@google.com>
Cc: Inseob Kim <inseob@google.com>,
linux-kernel@vger.kernel.org, changbin.du@gmail.com,
jbaron@akamai.com, joe@perches.com,
Josh Law <objecting@objecting.org>
Subject: Re: [PATCH v2] lib: parser: Fix match_wildcard to correctly handle trailing stars
Date: Fri, 27 Mar 2026 08:17:19 -0700 [thread overview]
Message-ID: <20260327081719.3185b24c9467ddbb0ed9397f@linux-foundation.org> (raw)
In-Reply-To: <CAKc0u47BK4N1A6zS04_dKiZt1PD6+pbrfEcmQTSRkpBJA-VE5Q@mail.gmail.com>
On Fri, 27 Mar 2026 19:11:21 +0900 Takaya Saeki <takayas@google.com> wrote:
> > Sorry for the confusion; let me correct myself. It's not that wildcard
> > is preferable to glob, but genfs_seclabel_wildcard is already merged
> > and in use so moving from wildcard to glob would introduce breaking
> > changes. Let me invite Takaya who possibly has more rationale for the
> > wildcard.
>
> Yes, there wasn't strong motivation to avoid glob; wildcards were sufficient,
> so we just didn't consider adopting glob.
> Since glob is a superset of wildcards and doesn't treat slashes as
> special characters,
> it would certainly be more convenient to use. We might want to improve SELinux
> later including the network interface matching, which also uses
> wildcard matching.
OK, thanks.
It isn't a big deal at all - I'm just wondering if we have an
opportunity to remove some code by migrating all wildcard users over to
glob.
next prev parent reply other threads:[~2026-03-27 15:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 2:06 Inseob Kim
2026-03-26 2:25 ` Andrew Morton
2026-03-26 4:12 ` Inseob Kim
2026-03-26 4:45 ` Andrew Morton
2026-03-26 4:51 ` Inseob Kim
2026-03-27 10:11 ` Takaya Saeki
2026-03-27 15:17 ` Andrew Morton [this message]
2026-03-26 7:10 ` Josh Law
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=20260327081719.3185b24c9467ddbb0ed9397f@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=changbin.du@gmail.com \
--cc=inseob@google.com \
--cc=jbaron@akamai.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=objecting@objecting.org \
--cc=takayas@google.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
all inboxes | Powered by JetHome®