All of lore.kernel.org
 help / color / mirror / Atom feed
From: jlayton@kernel.org (Jeff Layton)
To: linux-security-module@vger.kernel.org
Subject: [PATCH] integrity: get rid of unneeded initializations in integrity_iint_cache entries
Date: Thu, 07 Dec 2017 10:16:53 -0500	[thread overview]
Message-ID: <1512659813.1350.18.camel@kernel.org> (raw)
In-Reply-To: <1512657347.3527.48.camel@linux.vnet.ibm.com>

On Thu, 2017-12-07 at 09:35 -0500, Mimi Zohar wrote:
> On Thu, 2017-12-07 at 07:01 -0500, Jeff Layton wrote:
> > On Thu, 2017-07-06 at 15:43 -0400, Mimi Zohar wrote:
> > > On Thu, 2017-07-06 at 10:04 -0500, Serge E. Hallyn wrote:
> > > > Quoting Jeff Layton (jlayton at kernel.org):
> > > > > From: Jeff Layton <jlayton@redhat.com>
> > > > > 
> > > > > The init_once routine memsets the whole object to 0, and then
> > > > > explicitly sets some of the fields to 0 again. Just remove the explicit
> > > > > initializations.
> > > > > 
> > > > > Signed-off-by: Jeff Layton <jlayton@redhat.com>
> > > > 
> > > > Reviewed-by: Serge Hallyn <serge@hallyn.com>
> > > 
> > > Thanks, queued.
> > > 
> > > Mimi
> > > 
> > 
> > Hi Mimi,
> > 
> > I notice that this patch hasn't made the last couple of releases. Was it
> > dropped for some reason?
> 
> Thanks for the reminder.  I accidentally dropped it (and Sascha
> Hauer's patch).  The subject line is too long.  Assuming you don't
> object, I'll replace the "get rid of" with "removed" and queue the
> patch in the next-queued-testing branch.
> 
> Mimi
> 

Sounds good.

Thanks,
-- 
Jeff Layton <jlayton@kernel.org>
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: Jeff Layton <jlayton@kernel.org>
To: Mimi Zohar <zohar@linux.vnet.ibm.com>,
	"Serge E. Hallyn" <serge@hallyn.com>
Cc: linux-kernel@vger.kernel.org, linux-security-module@vger.kernel.org
Subject: Re: [PATCH] integrity: get rid of unneeded initializations in integrity_iint_cache entries
Date: Thu, 07 Dec 2017 10:16:53 -0500	[thread overview]
Message-ID: <1512659813.1350.18.camel@kernel.org> (raw)
In-Reply-To: <1512657347.3527.48.camel@linux.vnet.ibm.com>

On Thu, 2017-12-07 at 09:35 -0500, Mimi Zohar wrote:
> On Thu, 2017-12-07 at 07:01 -0500, Jeff Layton wrote:
> > On Thu, 2017-07-06 at 15:43 -0400, Mimi Zohar wrote:
> > > On Thu, 2017-07-06 at 10:04 -0500, Serge E. Hallyn wrote:
> > > > Quoting Jeff Layton (jlayton@kernel.org):
> > > > > From: Jeff Layton <jlayton@redhat.com>
> > > > > 
> > > > > The init_once routine memsets the whole object to 0, and then
> > > > > explicitly sets some of the fields to 0 again. Just remove the explicit
> > > > > initializations.
> > > > > 
> > > > > Signed-off-by: Jeff Layton <jlayton@redhat.com>
> > > > 
> > > > Reviewed-by: Serge Hallyn <serge@hallyn.com>
> > > 
> > > Thanks, queued.
> > > 
> > > Mimi
> > > 
> > 
> > Hi Mimi,
> > 
> > I notice that this patch hasn't made the last couple of releases. Was it
> > dropped for some reason?
> 
> Thanks for the reminder.  I accidentally dropped it (and Sascha
> Hauer's patch).  The subject line is too long.  Assuming you don't
> object, I'll replace the "get rid of" with "removed" and queue the
> patch in the next-queued-testing branch.
> 
> Mimi
> 

Sounds good.

Thanks,
-- 
Jeff Layton <jlayton@kernel.org>

  reply	other threads:[~2017-12-07 15:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-06 14:54 [PATCH] integrity: get rid of unneeded initializations in integrity_iint_cache entries Jeff Layton
2017-07-06 14:54 ` Jeff Layton
2017-07-06 15:04 ` Serge E. Hallyn
2017-07-06 15:04   ` Serge E. Hallyn
2017-07-06 19:43   ` Mimi Zohar
2017-07-06 19:43     ` Mimi Zohar
2017-12-07 12:01     ` Jeff Layton
2017-12-07 12:01       ` Jeff Layton
2017-12-07 14:35       ` Mimi Zohar
2017-12-07 14:35         ` Mimi Zohar
2017-12-07 15:16         ` Jeff Layton [this message]
2017-12-07 15:16           ` Jeff Layton

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=1512659813.1350.18.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=linux-security-module@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.