public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: John Johansen <john.johansen@canonical.com>
Cc: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
	"Serge E . Hallyn" <serge@hallyn.com>,
	linux-security-module@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Subject: Re: [PATCH 3/3] security/apparmor: do not define list_entry_next
Date: Thu, 19 Nov 2015 09:20:38 +0900	[thread overview]
Message-ID: <20151119002038.GA537@swordfish> (raw)
In-Reply-To: <564CC12A.2000505@canonical.com>

On (11/18/15 10:19), John Johansen wrote:
> On 11/18/2015 04:14 AM, Sergey Senozhatsky wrote:
> > Cosmetic.
> > 
> > Do not define list_entry_next() and use list_next_entry()
> > from list.h.
> > 
> 
> two days to late,
> 
> Geliang Tang already submitted the same patch in
> [PATCH 3/3] apparmor: use list_next_entry instead of list_entry_next
> 

Oh, wow. sorry for the noise. thanks.

	-ss

> and I've pulled it into my tree
> 
> still thank you for your work, it is appreciated
> 
> > Signed-off-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
> > ---
> >  security/apparmor/apparmorfs.c | 10 ++++------
> >  1 file changed, 4 insertions(+), 6 deletions(-)
> > 
> > diff --git a/security/apparmor/apparmorfs.c b/security/apparmor/apparmorfs.c
> > index ad4fa49..946e8fd 100644
> > --- a/security/apparmor/apparmorfs.c
> > +++ b/security/apparmor/apparmorfs.c
> > @@ -21,6 +21,7 @@
> >  #include <linux/namei.h>
> >  #include <linux/capability.h>
> >  #include <linux/rcupdate.h>
> > +#include <linux/list.h>
> >  
> >  #include "include/apparmor.h"
> >  #include "include/apparmorfs.h"
> > @@ -549,9 +550,6 @@ fail2:
> >  	return error;
> >  }
> >  
> > -
> > -#define list_entry_next(pos, member) \
> > -	list_entry(pos->member.next, typeof(*pos), member)
> >  #define list_entry_is_head(pos, head, member) (&pos->member == (head))
> >  
> >  /**
> > @@ -582,7 +580,7 @@ static struct aa_namespace *__next_namespace(struct aa_namespace *root,
> >  	parent = ns->parent;
> >  	while (ns != root) {
> >  		mutex_unlock(&ns->lock);
> > -		next = list_entry_next(ns, base.list);
> > +		next = list_next_entry(ns, base.list);
> >  		if (!list_entry_is_head(next, &parent->sub_ns, base.list)) {
> >  			mutex_lock(&next->lock);
> >  			return next;
> > @@ -636,7 +634,7 @@ static struct aa_profile *__next_profile(struct aa_profile *p)
> >  	parent = rcu_dereference_protected(p->parent,
> >  					   mutex_is_locked(&p->ns->lock));
> >  	while (parent) {
> > -		p = list_entry_next(p, base.list);
> > +		p = list_next_entry(p, base.list);
> >  		if (!list_entry_is_head(p, &parent->base.profiles, base.list))
> >  			return p;
> >  		p = parent;
> > @@ -645,7 +643,7 @@ static struct aa_profile *__next_profile(struct aa_profile *p)
> >  	}
> >  
> >  	/* is next another profile in the namespace */
> > -	p = list_entry_next(p, base.list);
> > +	p = list_next_entry(p, base.list);
> >  	if (!list_entry_is_head(p, &ns->base.profiles, base.list))
> >  		return p;
> >  
> > 
> 

      reply	other threads:[~2015-11-19  0:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-18 12:14 [PATCH 3/3] security/apparmor: do not define list_entry_next Sergey Senozhatsky
2015-11-18 18:19 ` John Johansen
2015-11-19  0:20   ` Sergey Senozhatsky [this message]

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=20151119002038.GA537@swordfish \
    --to=sergey.senozhatsky.work@gmail.com \
    --cc=john.johansen@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=serge@hallyn.com \
    --cc=sergey.senozhatsky@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