public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Fanael Linithien <fanael4@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: Verifier fixes backported to stable kernels?
Date: Mon, 11 Aug 2014 17:16:29 +1000	[thread overview]
Message-ID: <20140811071629.GK26465@dastard> (raw)
In-Reply-To: <20140811043219.GJ26465@dastard>

On Mon, Aug 11, 2014 at 02:32:19PM +1000, Dave Chinner wrote:
> On Sat, Aug 09, 2014 at 05:55:19PM +0200, Fanael Linithien wrote:
> > 2014-08-09 2:54 GMT+02:00 Dave Chinner <david@fromorbit.com>:
> > > What fixes are you talking about? List of commits, please, noting
> > > whether the commit already has a "cc: <stable@vger.kernel.org>" in
> > > it or not.
> > 
> > These are the commits:
> > 
> > 400b9d88757c0bfbdfa97014e090ec40a31c1282
> > 67dc288c21064b31a98a53dc64f6b9714b819fd6 (this is the only one with the cc)
> > 5fd364fee81a7888af806e42ed8a91c845894f2d
> > ad3714b82c631a34724da09a7daa53afcab952fa
> 
> Ok, but please use the "one-line format" when quoting commits.
> 
> I.e. this:
> 
> $ git log --oneline -n 4 ad3714b
> ad3714b xfs: dquot recovery needs verifiers
> 5fd364f xfs: quotacheck leaves dquot buffers without verifiers
> 67dc288 xfs: ensure verifiers are attached to recovered buffers
> 400b9d8 xfs: catch buffers written without verifiers attached

Actually, I'm not going to send this last patch back to older,
stable kernels. I really don't want to have to port random patches
back to older kernels to avoid it generating false positives.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2014-08-11  7:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-08 19:23 Verifier fixes backported to stable kernels? Fanael Linithien
2014-08-09  0:54 ` Dave Chinner
     [not found]   ` <CA+o=1OX+Qq4Scq=su1MDDknRXJGL8F=7WV8P0PCeDjYep7rLnA@mail.gmail.com>
2014-08-09 15:55     ` Fanael Linithien
2014-08-09 18:58       ` Eric Sandeen
2014-08-11  4:32       ` Dave Chinner
2014-08-11  7:16         ` Dave Chinner [this message]
     [not found]         ` <CA+o=1OUEJimqFngui01JvvS3YjwCOimpWTu+A2MPkYBmq0xgiQ@mail.gmail.com>
2014-08-11 16:19           ` Fanael Linithien

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=20140811071629.GK26465@dastard \
    --to=david@fromorbit.com \
    --cc=fanael4@gmail.com \
    --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