All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Viro <aviro@redhat.com>
To: Alexander Viro <aviro@redhat.com>
Cc: linux-audit@redhat.com
Subject: Re: [PATCH] log more info for directory entry change events
Date: Fri, 9 Jun 2006 09:13:07 -0400	[thread overview]
Message-ID: <20060609131307.GE22634@devserv.devel.redhat.com> (raw)
In-Reply-To: <20060609131113.GD22634@devserv.devel.redhat.com>

On Fri, Jun 09, 2006 at 09:11:13AM -0400, Alexander Viro wrote:
> On Thu, Jun 08, 2006 at 11:19:31PM -0400, Amy Griffis wrote:
> 
> > +extern const char *	    audit_log_n_untrustedstring(struct audit_buffer *ab,
> > +							unsigned n,
> > +							const char *string);
> 
> > +static void audit_log_n_string(struct audit_buffer *ab, size_t slen,
> > +			       const char *string)


Er...
> +const char *audit_log_n_untrustedstring(struct audit_buffer *ab, size_t len,
> +                                       const char *string)

actually.

> ... and size_t != unsigned.  Fixed in git tree.

  reply	other threads:[~2006-06-09 13:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-09  3:19 [PATCH] log more info for directory entry change events Amy Griffis
2006-06-09 13:11 ` Alexander Viro
2006-06-09 13:13   ` Alexander Viro [this message]
2006-06-12 16:38     ` Amy Griffis

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=20060609131307.GE22634@devserv.devel.redhat.com \
    --to=aviro@redhat.com \
    --cc=linux-audit@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 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.