public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Alexander Viro <aviro@redhat.com>
To: Steve Grubb <sgrubb@redhat.com>
Cc: Linux Audit <linux-audit@redhat.com>
Subject: Re: [PATCH] name_count array overrun
Date: Fri, 29 Sep 2006 08:46:04 -0400	[thread overview]
Message-ID: <20060929124604.GN17710@devserv.devel.redhat.com> (raw)
In-Reply-To: <200609281431.32535.sgrubb@redhat.com>

On Thu, Sep 28, 2006 at 02:31:32PM -0400, Steve Grubb wrote:
> Hi,
> 
> This patch removes the rdev logging from the previous patch
> 
> The below patch closes an unbounded use of name_count. This can lead to oopses
> in some new file systems.
> 
> Signed-off-by: Steve Grubb <sgrubb@redhat.com>
 
ACK, but please repost with a mailer that wouldn't eat patches.  It's
got serious tab damage.

  reply	other threads:[~2006-09-29 12:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-28 18:31 [PATCH] name_count array overrun Steve Grubb
2006-09-29 12:46 ` Alexander Viro [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-09-07 18:00 Steve Grubb
2006-09-07 20:43 ` Amy Griffis
2006-09-07 20:53   ` Steve Grubb
2006-09-24 12:56   ` Steve Grubb
2006-09-27 21:04     ` 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=20060929124604.GN17710@devserv.devel.redhat.com \
    --to=aviro@redhat.com \
    --cc=linux-audit@redhat.com \
    --cc=sgrubb@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