From: Richard Guy Briggs <rgb@redhat.com>
To: Paul Moore <paul@paul-moore.com>
Cc: Linux-Audit Mailing List <linux-audit@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org, Eric Paris <eparis@parisplace.org>,
Steve Grubb <sgrubb@redhat.com>, Jan Kara <jack@suse.cz>
Subject: Re: [PATCH v2 1/3] fanotify: Ensure consistent variable type for response
Date: Tue, 3 May 2022 17:07:39 -0400 [thread overview]
Message-ID: <YnGZmw8yuD+6ON29@madcap2.tricolour.ca> (raw)
In-Reply-To: <CAHC9VhSFOx1d_7-XnbobjZXjps_mXq3S33T_5E=PmNAeyqAsdw@mail.gmail.com>
On 2022-05-02 20:16, Paul Moore wrote:
> On Thu, Apr 28, 2022 at 8:45 PM Richard Guy Briggs <rgb@redhat.com> wrote:
> >
> > The user space API for the response variable is __u32. This patch makes
> > sure that the whole path through the kernel uses __u32 so that there is
> > no sign extension or truncation of the user space response.
> >
> > Suggested-by: Steve Grubb <sgrubb@redhat.com>
> > Link: https://lore.kernel.org/r/12617626.uLZWGnKmhe@x2
> > Signed-off-by: Richard Guy Briggs <rgb@redhat.com>
> > Link: https://lore.kernel.org/r/aa98a3ad00666a6fc0ce411755de4a1a60f5c0cd.1651174324.git.rgb@redhat.com
> > ---
> > fs/notify/fanotify/fanotify.h | 2 +-
> > fs/notify/fanotify/fanotify_user.c | 6 +++---
> > 2 files changed, 4 insertions(+), 4 deletions(-)
>
> It seems like audit_fanotify()/__audit_fanotify() should also be
> changed, yes? Granted, in this case it's an unsigned int to u32
> conversion so not really all that critical, but if you are going to
> update the fanotify code you might as well update the audit code as
> well for the sake of completeness.
Yes, that was somewhere in the back of my mind but forgot to come back
to it. Thanks for catching that.
> paul-moore.com
- RGB
--
Richard Guy Briggs <rgb@redhat.com>
Sr. S/W Engineer, Kernel Security, Base Operating Systems
Remote, Ottawa, Red Hat Canada
IRC: rgb, SunRaycer
Voice: +1.647.777.2635, Internal: (81) 32635
next prev parent reply other threads:[~2022-05-03 21:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 0:44 [PATCH v2 0/3] fanotify: Allow user space to pass back additional audit info Richard Guy Briggs
2022-04-29 0:44 ` [PATCH v2 1/3] fanotify: Ensure consistent variable type for response Richard Guy Briggs
2022-05-03 0:16 ` Paul Moore
2022-05-03 21:07 ` Richard Guy Briggs [this message]
2022-04-29 0:44 ` [PATCH v2 2/3] fanotify: define struct members to hold response decision context Richard Guy Briggs
2022-05-03 0:16 ` Paul Moore
2022-05-04 1:33 ` Richard Guy Briggs
2022-05-05 3:32 ` Paul Moore
2022-05-05 14:44 ` Jan Kara
2022-05-05 17:34 ` Amir Goldstein
2022-05-06 8:35 ` Jan Kara
2022-05-05 22:43 ` Steve Grubb
2022-05-06 18:46 ` Richard Guy Briggs
2022-05-09 8:54 ` Jan Kara
2022-05-16 20:53 ` Richard Guy Briggs
2022-04-29 0:44 ` [PATCH v2 3/3] fanotify: Allow audit to use the full permission event response Richard Guy Briggs
2022-05-03 0:16 ` Paul Moore
2022-04-29 0:55 ` [PATCH v2 0/3] fanotify: Allow user space to pass back additional audit info Richard Guy Briggs
2022-05-03 0:16 ` Paul Moore
2022-05-03 21:00 ` Richard Guy Briggs
2022-05-03 20:57 ` Steve Grubb
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=YnGZmw8yuD+6ON29@madcap2.tricolour.ca \
--to=rgb@redhat.com \
--cc=eparis@parisplace.org \
--cc=jack@suse.cz \
--cc=linux-audit@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=sgrubb@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
all inboxes | Powered by JetHome®