stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Josh Boyer <jwboyer@fedoraproject.org>
Cc: Luis Henriques <luis.henriques@canonical.com>,
	Kees Cook <keescook@google.com>,
	Dwight Engen <dwight.engen@oracle.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Brian Foster <bfoster@redhat.com>,
	Dave Chinner <dchinner@redhat.com>,
	Gao feng <gaofeng@cn.fujitsu.com>, Ben Myers <bpm@sgi.com>,
	Greg KH <gregkh@linuxfoundation.org>,
	xfs@oss.sgi.com,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: XFS security fix never sent to -stable?
Date: Wed, 11 Dec 2013 13:00:07 +1100	[thread overview]
Message-ID: <20131211020007.GH10988@dastard> (raw)
In-Reply-To: <CA+5PVA7wso5fo11xX9kCUdbrqBQMzUnYwTOB_Qe3K7LDY4z_Cw@mail.gmail.com>

On Tue, Dec 10, 2013 at 08:10:51PM -0500, Josh Boyer wrote:
> On Tue, Dec 10, 2013 at 8:03 PM, Dave Chinner <david@fromorbit.com> wrote:
> > Security processes are not something that should be hidden away in
> > it's own private corner - if there's a problem upstream needs to
> > take action on, then direct contact with upstream is necessary. We
> > need to know about security issues - even ones that are classified
> > post-commit as security issues - so we are operating with full
> > knowledge of the issues in our code and the impact of our fixes....
> 
> Agreed.  I'm going to interpret your comments at being directed to the
> general audience because otherwise you're just shooting the messenger
> :).

Right, they are not aimed at you - they are aimed at those on the
security side of the fence. I'm tired of learning about CVEs in XFS
code through chinese whispers and/or luck.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  reply	other threads:[~2013-12-11  2:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAGXu5jLKkgYg5UWJc8xBGN5NgDh68Q3YRxO--zmDL86BWPH78A@mail.gmail.com>
     [not found] ` <20131209121534.GE4278@hercules>
     [not found]   ` <CA+5PVA4ychvLEi1ZZ6rYy2=5-wZAbQ_a-aoy8=1w3+tr-pt3Fg@mail.gmail.com>
2013-12-09 23:55     ` XFS security fix never sent to -stable? Dave Chinner
2013-12-10  7:56       ` Greg KH
2013-12-10 13:15         ` Josh Boyer
2013-12-10 14:31           ` Eric Sandeen
2013-12-10 15:57             ` Ben Myers
2013-12-17 13:58         ` Luis Henriques
2013-12-10 13:20       ` Josh Boyer
2013-12-11  1:03         ` Dave Chinner
2013-12-11  1:10           ` Josh Boyer
2013-12-11  2:00             ` Dave Chinner [this message]
2013-12-11  2:12               ` Greg KH
2013-12-11  2:45               ` Kees Cook
2013-12-11  4:17                 ` Dave Chinner
2013-12-11  8:27                   ` Dan Carpenter

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=20131211020007.GH10988@dastard \
    --to=david@fromorbit.com \
    --cc=bfoster@redhat.com \
    --cc=bpm@sgi.com \
    --cc=dchinner@redhat.com \
    --cc=dwight.engen@oracle.com \
    --cc=gaofeng@cn.fujitsu.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jwboyer@fedoraproject.org \
    --cc=keescook@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luis.henriques@canonical.com \
    --cc=stable@vger.kernel.org \
    --cc=xfs@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).