From: Jiri Slaby <jslaby@suse.cz>
To: Nikolay Borisov <n.borisov.lkml@gmail.com>, stable@vger.kernel.org
Cc: darrick.wong@oracle.com, linux-xfs@vger.kernel.org, bfoster@redhat.com
Subject: Re: Consider including ef388e2054fe ("xfs: don't allow di_size with high bit set") into stable releases
Date: Mon, 27 Mar 2017 10:18:18 +0200 [thread overview]
Message-ID: <666a6b51-1f2f-d175-6c39-c7475125c045@suse.cz> (raw)
In-Reply-To: <53efcbd6-289e-3b71-3d47-73d2b06b98ba@gmail.com>
On 03/27/2017, 09:43 AM, Nikolay Borisov wrote:
> Hello,
>
>
> The patch in the subject applies cleanly on 4.4 and I have attached the
> backport for 3.12. This causes hangs in both xfs/133 and xfs/134. As is
> customary - a battery of xfstests have been run to ensure no regressions
> were introduced.
Applied to 3.12, thanks!
--
js
suse labs
prev parent reply other threads:[~2017-03-27 8:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 7:43 Consider including ef388e2054fe ("xfs: don't allow di_size with high bit set") into stable releases Nikolay Borisov
2017-03-27 8:18 ` Jiri Slaby [this message]
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=666a6b51-1f2f-d175-6c39-c7475125c045@suse.cz \
--to=jslaby@suse.cz \
--cc=bfoster@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=linux-xfs@vger.kernel.org \
--cc=n.borisov.lkml@gmail.com \
--cc=stable@vger.kernel.org \
/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).