From: Nikolay Borisov <n.borisov.lkml@gmail.com>
To: stable@vger.kernel.org
Cc: darrick.wong@oracle.com, linux-xfs@vger.kernel.org, david@fromorbit.com
Subject: Request for including dbd5c8c9a288 ("xfs: pass total block res. as total xfs_bmapi_write() parameter") into stable
Date: Wed, 15 Mar 2017 12:41:02 +0200 [thread overview]
Message-ID: <153397e1-ba41-20b3-455e-d622c234bc3a@gmail.com> (raw)
Hello,
I'd like to request the commit from the subject to be included into
stable kernels, starting with 3.12. Without generic/299 would deadlock
almost always, whereas with the commit applied I can get it to run 20
consecutive times without a hitch.
Regards,
Nikolay
next reply other threads:[~2017-03-15 10:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-15 10:41 Nikolay Borisov [this message]
2017-03-15 11:54 ` Request for including dbd5c8c9a288 ("xfs: pass total block res. as total xfs_bmapi_write() parameter") into stable Brian Foster
2017-03-15 12:24 ` xfs: pass total block res. as total xfs_bmapi_write() parameter Nikolay Borisov
2017-03-15 15:00 ` Brian Foster
2017-03-16 10:07 ` Jiri Slaby
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=153397e1-ba41-20b3-455e-d622c234bc3a@gmail.com \
--to=n.borisov.lkml@gmail.com \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=linux-xfs@vger.kernel.org \
--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).