From: Greg KH <gregkh@linuxfoundation.org>
To: Ajay Kaher <akaher@vmware.com>
Cc: "dchinner@redhat.com" <dchinner@redhat.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
Steven Rostedt <srostedt@vmware.com>,
Srivatsa Bhat <srivatsab@vmware.com>,
"srivatsa@csail.mit.edu" <srivatsa@csail.mit.edu>,
Alexey Makhalov <amakhalov@vmware.com>,
Srinidhi Rao <srinidhir@vmware.com>,
Vikash Bansal <bvikas@vmware.com>,
Anish Swaminathan <anishs@vmware.com>,
Vasavi Sirnapalli <vsirnapalli@vmware.com>,
"Darrick J . Wong" <darrick.wong@oracle.com>
Subject: Re: [4.9.y PATCH] xfs: clear sb->s_fs_info on mount failure
Date: Wed, 16 Oct 2019 14:22:09 -0700 [thread overview]
Message-ID: <20191016212209.GE856391@kroah.com> (raw)
In-Reply-To: <F4C3D25C-A8FC-4A31-8CC2-1ABBA6CDF1C1@vmware.com>
On Wed, Oct 09, 2019 at 05:54:36PM +0000, Ajay Kaher wrote:
>
>
> On 08/10/19, 11:18 PM, "Greg KH" <gregkh@linuxfoundation.org> wrote:
>
> > On Wed, Oct 02, 2019 at 02:53:51AM +0530, Ajay Kaher wrote:
> > > From: Dave Chinner <dchinner@redhat.com>
> > >
> > > commit c9fbd7bbc23dbdd73364be4d045e5d3612cf6e82 upstream.
>
> > You have sent a 4.4.y and 4.9.y, but what about 4.14.y? I can't take
> > this patch for the older kernels without a 4.14.y patch, sorry. We
> > don't want anyone to upgrade and then hit a fixed bug.
>
> Sent for 4.14.y as well. Thanks for specifying about 4.14.y for this patch.
Thanks for that, now queued up for all 3 trees.
greg k-h
next prev parent reply other threads:[~2019-10-16 21:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-01 21:23 [4.9.y PATCH] xfs: clear sb->s_fs_info on mount failure Ajay Kaher
2019-10-08 17:47 ` Greg KH
2019-10-09 17:54 ` Ajay Kaher
2019-10-16 21:22 ` Greg KH [this message]
2019-10-17 16:37 ` Ajay Kaher
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=20191016212209.GE856391@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akaher@vmware.com \
--cc=amakhalov@vmware.com \
--cc=anishs@vmware.com \
--cc=bvikas@vmware.com \
--cc=darrick.wong@oracle.com \
--cc=dchinner@redhat.com \
--cc=srinidhir@vmware.com \
--cc=srivatsa@csail.mit.edu \
--cc=srivatsab@vmware.com \
--cc=srostedt@vmware.com \
--cc=stable@vger.kernel.org \
--cc=vsirnapalli@vmware.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.