public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Paul Moore <pmoore@redhat.com>
To: Richard Guy Briggs <rgb@redhat.com>
Cc: linux-audit@redhat.com
Subject: Re: [PATCH] audit: we don't need to __set_current_state(TASK_RUNNING)
Date: Wed, 06 Apr 2016 13:41:33 -0400	[thread overview]
Message-ID: <3491398.aapD2cfJyo@sifl> (raw)
In-Reply-To: <20160406165624.GH19769@madcap2.tricolour.ca>

On Wednesday, April 06, 2016 12:56:24 PM Richard Guy Briggs wrote:
> On 16/04/05, Paul Moore wrote:
> > From: Paul Moore <paul@paul-moore.com>
> > 
> > Remove the calls to __set_current_state() to mark the task as running
> > and do some related cleanup in wait_for_auditd() to limit the amount
> > of work we do when we aren't going to reschedule the current task.
> 
> Wow, the logic of this goes back to 9ad9ad38 (2005-06-22, AUDIT: Wait
> for backlog to clear when generating messages.)

Yeah, I didn't think much of it until Jiri submitted that last patch and 
figured I should check how we were doing handling the rescheduling in the rest 
of the code.  I think it stayed the way it was for so long because technically 
it wasn't hurting anything.

> > Signed-off-by: Paul Moore <paul@paul-moore.com>
> 
> These changes look good to me.
> 
> > ---
> > 
> >  kernel/audit.c |   12 +++++-------
> >  1 file changed, 5 insertions(+), 7 deletions(-)
> > 
> > diff --git a/kernel/audit.c b/kernel/audit.c
> > index 3a3e5de..f52fbef 100644
> > --- a/kernel/audit.c
> > +++ b/kernel/audit.c
> > 
> > @@ -430,7 +430,6 @@ restart:
> >  					attempts, audit_pid);
> >  				
> >  				set_current_state(TASK_INTERRUPTIBLE);
> >  				schedule();
> > 
> > -				__set_current_state(TASK_RUNNING);
> > 
> >  				goto restart;
> >  			
> >  			}
> >  		
> >  		}
> > 
> > @@ -1324,15 +1323,14 @@ static inline void audit_get_stamp(struct
> > audit_context *ctx,> 
> >  static long wait_for_auditd(long sleep_time)
> >  {
> >  
> >  	DECLARE_WAITQUEUE(wait, current);
> > 
> > -	set_current_state(TASK_UNINTERRUPTIBLE);
> > -	add_wait_queue_exclusive(&audit_backlog_wait, &wait);
> > 
> >  	if (audit_backlog_limit &&
> > 
> > -	    skb_queue_len(&audit_skb_queue) > audit_backlog_limit)
> > +	    skb_queue_len(&audit_skb_queue) > audit_backlog_limit) {
> > +		add_wait_queue_exclusive(&audit_backlog_wait, &wait);
> > +		set_current_state(TASK_UNINTERRUPTIBLE);
> > 
> >  		sleep_time = schedule_timeout(sleep_time);
> > 
> > -
> > -	__set_current_state(TASK_RUNNING);
> > -	remove_wait_queue(&audit_backlog_wait, &wait);
> > +		remove_wait_queue(&audit_backlog_wait, &wait);
> > +	}
> > 
> >  	return sleep_time;
> >  
> >  }
> 
> - RGB
> 
> --
> Richard Guy Briggs <rbriggs@redhat.com>
> Senior Software Engineer, Kernel Security, AMER ENG Base Operating Systems,
> Red Hat Remote, Ottawa, Canada
> Voice: +1.647.777.2635, Internal: (81) 32635, Alt: +1.613.693.0684x3545

-- 
paul moore
security @ redhat

      reply	other threads:[~2016-04-06 17:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-05 18:31 [PATCH] audit: we don't need to __set_current_state(TASK_RUNNING) Paul Moore
2016-04-06 16:56 ` Richard Guy Briggs
2016-04-06 17:41   ` Paul Moore [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=3491398.aapD2cfJyo@sifl \
    --to=pmoore@redhat.com \
    --cc=linux-audit@redhat.com \
    --cc=rgb@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