selinux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rahul Sandhu" <nvraxn@gmail.com>
To: <stephen.smalley.work@gmail.com>
Cc: <jwcart2@gmail.com>, <nvraxn@gmail.com>, <omosnace@redhat.com>,
	<paul@paul-moore.com>, <plautrba@redhat.com>,
	<selinux@vger.kernel.org>
Subject: Re: [PATCH v4] libselinux: fix parsing of the enforcing kernel cmdline parameter
Date: Fri, 25 Jul 2025 23:03:09 +0100	[thread overview]
Message-ID: <DBLH4U3X4LOW.1MQVO4THRG7CS@gmail.com> (raw)
In-Reply-To: <CAEjxPJ6nRZ50-L5wDtnppC641OjuEzO8QRUhGjJXcT5iKTNfbQ@mail.gmail.com>

> Apologies for not asking this earlier, but is there a reason you only
> increment tmp by 1 versus by sizeof("enforcing=")-1?

No specific reason, I guess that's also more efficient so v5 incoming.

  reply	other threads:[~2025-07-25 22:03 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-20 12:52 [PATCH] libselinux: fix parsing of the enforcing kernel cmdline parameter Rahul Sandhu
2025-07-21  9:01 ` robinshao007
2025-07-21  9:47   ` Rahul Sandhu
2025-07-21  9:58     ` robinshao007
2025-07-21 12:56 ` Stephen Smalley
2025-07-21 14:18   ` Stephen Smalley
2025-07-22  5:42     ` Rahul Sandhu
2025-07-22 13:05       ` Stephen Smalley
2025-07-22 15:36         ` Stephen Smalley
2025-07-24  9:13   ` [PATCH v2] " Rahul Sandhu
2025-07-24 12:28     ` Stephen Smalley
2025-07-24 12:33       ` Rahul Sandhu
2025-07-24 13:05       ` [PATCH v3] " Rahul Sandhu
2025-07-24 13:27         ` Stephen Smalley
2025-07-24 13:30           ` Stephen Smalley
2025-07-24 13:51           ` [PATCH v4] " Rahul Sandhu
2025-07-24 19:29             ` Stephen Smalley
2025-07-25 22:03               ` Rahul Sandhu [this message]
2025-07-25 22:15               ` [PATCH v5] " Rahul Sandhu
2025-07-28 14:04                 ` Stephen Smalley
2025-07-30 13:06                   ` 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=DBLH4U3X4LOW.1MQVO4THRG7CS@gmail.com \
    --to=nvraxn@gmail.com \
    --cc=jwcart2@gmail.com \
    --cc=omosnace@redhat.com \
    --cc=paul@paul-moore.com \
    --cc=plautrba@redhat.com \
    --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;
as well as URLs for NNTP newsgroup(s).