From: Johannes Segitz <jsegitz@suse.de>
To: Stephen Smalley <stephen.smalley.work@gmail.com>
Cc: selinux@vger.kernel.org
Subject: Re: [PATCH] selinux_restorecon: Do not exit on directory cycles
Date: Tue, 21 Jul 2026 17:15:06 +0200 [thread overview]
Message-ID: <al-M-kE18Q7okHxy@suse.com> (raw)
In-Reply-To: <CAEjxPJ7+=671kRb2fxSgZsyDuysDatMamUZT_vtFkug6_5x2nQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 856 bytes --]
On Tue, Jul 21, 2026 at 09:54:28AM -0400, Stephen Smalley wrote:
> On Tue, Jul 21, 2026 at 3:23 AM Johannes Segitz <jsegitz@suse.de> wrote:
> >
> > All other failures are handled gracefully. Directory cycles can e.g.
> > happen on BTRFS filesystems with subvolumes. Skip them and continue
> > instead of exiting
> >
> > Signed-off-by: Johannes Segitz <jsegitz@suse.de>
>
> This doesn't apply on selinux/main.
Sorry, had a repo still with branch "master", will send both again tomorrow
Johannes
--
GPG Key EE16 6BCE AD56 E034 BFB3 3ADD 7BF7 29D5 E7C8 1FA0
Subkey fingerprint: 250F 43F5 F7CE 6F1E 9C59 4F95 BC27 DD9D 2CC4 FD66
SUSE Software Solutions Germany GmbH, Frankenstr. 146, 90461 Nürnberg, Germany
www.suse.com, Geschäftsführer: Jochen Jaser, Andrew McDonald, Abhinav Puri, (HRB 36809, AG Nürnberg)
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 870 bytes --]
next prev parent reply other threads:[~2026-07-21 15:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 7:17 [PATCH] selinux_restorecon: Do not exit on directory cycles Johannes Segitz
2026-07-21 13:54 ` Stephen Smalley
2026-07-21 15:15 ` Johannes Segitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-07-23 8:55 Johannes Segitz
2026-07-23 14:55 ` Stephen Smalley
2026-07-23 15:21 ` Johannes Segitz
2026-07-23 15:38 ` Stephen Smalley
2026-07-23 15:42 ` Johannes Segitz
2026-07-24 15:29 ` Stephen Smalley
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=al-M-kE18Q7okHxy@suse.com \
--to=jsegitz@suse.de \
--cc=selinux@vger.kernel.org \
--cc=stephen.smalley.work@gmail.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