From: Serge Hallyn <serge.hallyn-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org>
To: Aristeu Rozanski <aris-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Serge Hallyn
<serge.hallyn-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>,
Li Zefan <lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH] device_cgroup: fix the comment format for recently added functions
Date: Mon, 28 Apr 2014 20:31:03 +0000 [thread overview]
Message-ID: <20140428203103.GB26218@ubuntumail> (raw)
In-Reply-To: <20140424193321.GS29214-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Quoting Aristeu Rozanski (aris-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org):
> Moving more extensive explanations to the end of the comment.
>
> Cc: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
> Cc: Serge Hallyn <serge.hallyn-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
Acked-by: Serge E. Hallyn <serge.hallyn-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org>
> Cc: Li Zefan <lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
> Signed-off-by: Aristeu Rozanski <arozansk-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> ---
> security/device_cgroup.c | 33 ++++++++++++++++-----------------
> 1 files changed, 16 insertions(+), 17 deletions(-)
>
> diff --git a/security/device_cgroup.c b/security/device_cgroup.c
> index abbe0b2..dbd2489 100644
> --- a/security/device_cgroup.c
> +++ b/security/device_cgroup.c
> @@ -306,17 +306,17 @@ static int devcgroup_seq_show(struct seq_file *m, void *v)
> }
>
> /**
> - * match_exception - iterates the exception list trying to match a rule
> - * based on type, major, minor and access type. It is
> - * considered a match if an exception is found that
> - * will contain the entire range of provided parameters.
> + * match_exception - iterates the exception list trying to find a complete match
> * @exceptions: list of exceptions
> * @type: device type (DEV_BLOCK or DEV_CHAR)
> * @major: device file major number, ~0 to match all
> * @minor: device file minor number, ~0 to match all
> * @access: permission mask (ACC_READ, ACC_WRITE, ACC_MKNOD)
> *
> - * returns: true in case it matches an exception completely
> + * It is considered a complete match if an exception is found that will
> + * contain the entire range of provided parameters.
> + *
> + * Return: true in case it matches an exception completely
> */
> static bool match_exception(struct list_head *exceptions, short type,
> u32 major, u32 minor, short access)
> @@ -341,20 +341,19 @@ static bool match_exception(struct list_head *exceptions, short type,
> }
>
> /**
> - * match_exception_partial - iterates the exception list trying to match a rule
> - * based on type, major, minor and access type. It is
> - * considered a match if an exception's range is
> - * found to contain *any* of the devices specified by
> - * provided parameters. This is used to make sure no
> - * extra access is being granted that is forbidden by
> - * any of the exception list.
> + * match_exception_partial - iterates the exception list trying to find a partial match
> * @exceptions: list of exceptions
> * @type: device type (DEV_BLOCK or DEV_CHAR)
> * @major: device file major number, ~0 to match all
> * @minor: device file minor number, ~0 to match all
> * @access: permission mask (ACC_READ, ACC_WRITE, ACC_MKNOD)
> *
> - * returns: true in case the provided range mat matches an exception completely
> + * It is considered a partial match if an exception's range is found to
> + * contain *any* of the devices specified by provided parameters. This is
> + * used to make sure no extra access is being granted that is forbidden by
> + * any of the exception list.
> + *
> + * Return: true in case the provided range mat matches an exception completely
> */
> static bool match_exception_partial(struct list_head *exceptions, short type,
> u32 major, u32 minor, short access)
> @@ -387,13 +386,13 @@ static bool match_exception_partial(struct list_head *exceptions, short type,
> }
>
> /**
> - * verify_new_ex - verifies if a new exception is part of what is allowed
> - * by a dev cgroup based on the default policy +
> - * exceptions. This is used to make sure a child cgroup
> - * won't have more privileges than its parent
> + * verify_new_ex - verifies if a new exception is allowed by parent cgroup's permissions
> * @dev_cgroup: dev cgroup to be tested against
> * @refex: new exception
> * @behavior: behavior of the exception's dev_cgroup
> + *
> + * This is used to make sure a child cgroup won't have more privileges
> + * than its parent
> */
> static bool verify_new_ex(struct dev_cgroup *dev_cgroup,
> struct dev_exception_item *refex,
> --
> 1.7.1
>
next prev parent reply other threads:[~2014-04-28 20:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 19:33 [PATCH] device_cgroup: fix the comment format for recently added functions Aristeu Rozanski
[not found] ` <20140424193321.GS29214-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-04-28 20:31 ` Serge Hallyn [this message]
2014-05-02 15:30 ` Tejun Heo
[not found] ` <20140502153028.GG10204-Gd/HAXX7CRxy/B6EtB590w@public.gmane.org>
2014-05-02 15:49 ` Aristeu Rozanski
[not found] ` <20140502154959.GH29214-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-05-04 19:19 ` Tejun Heo
2014-05-04 19:21 ` Tejun Heo
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=20140428203103.GB26218@ubuntumail \
--to=serge.hallyn-gewih/nmzzlqt0dzr+alfa@public.gmane.org \
--cc=aris-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org \
--cc=serge.hallyn-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org \
--cc=tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
/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