From: Willy Tarreau <w@1wt.eu>
To: Greg KH <greg@kroah.com>
Cc: "Thomas D." <whissi@whissi.de>,
spender@grsecurity.net, stable@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: Something badly broken with the latest XFS changeset in all stable kernels?
Date: Wed, 15 Jun 2016 07:28:31 +0200 [thread overview]
Message-ID: <20160615052831.GA3452@1wt.eu> (raw)
In-Reply-To: <20160615013056.GA23074@kroah.com>
On Tue, Jun 14, 2016 at 06:30:56PM -0700, Greg KH wrote:
> As the patch was tagged with 3.10+, I assumed that it was safe to be
> merged to those older kernels, otherwise I would never have done so. We
> do have ways to mark external things like this for stable patches, it's
> a great help when doing backports.
I guess only 3.14.72 was affected in the end. 3.18.35 has the fix but my
understanding is that after 3.17 it's OK. Apparently it's not yet queued
for 3.16. Jiri has queued it for 3.12 but not yet released it. For 3.10
I only pick patches that are already in a 3.14 release so I didn't have
the time to backport it to 3.10 yet as the preview started before the
release. Overall the regression lived only 8 days in a single branch, I
guess it shows that our process works rather well and limits the exposure
to regressions.
Brad, it would have been nice to report it to the stable team especially
since you rely on these kernels for yours as well.
Regards,
Willy
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2016-06-15 5:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-13 21:57 Something badly broken with the latest XFS changeset in all stable kernels? Thomas D.
2016-06-15 0:02 ` Dave Chinner
2016-06-15 1:30 ` Greg KH
2016-06-15 5:28 ` Willy Tarreau [this message]
2016-06-15 6:51 ` Dave Chinner
2016-06-15 7:14 ` Willy Tarreau
2016-06-15 7:00 ` Jiri Slaby
2016-06-15 6:40 ` Dave Chinner
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=20160615052831.GA3452@1wt.eu \
--to=w@1wt.eu \
--cc=greg@kroah.com \
--cc=spender@grsecurity.net \
--cc=stable@vger.kernel.org \
--cc=whissi@whissi.de \
--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