From: Siddharth Chandrasekaran <siddharth@embedjournal.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Siddharth Chandrasekaran <csiddharth@vmware.com>,
srostedt@vmware.com, linux-kernel@vger.kernel.org,
stable@kernel.org, srivatsab@vmware.com, dchinner@redhat.com,
darrick.wong@oracle.com
Subject: Re: [PATCH] Backport security fixe to 4.9 and 4.4 stable trees
Date: Fri, 15 May 2020 18:59:43 +0530 [thread overview]
Message-ID: <20200515132943.GA97579@csiddharth-a01.vmware.com> (raw)
In-Reply-To: <20200515125701.GA1934886@kroah.com>
On Fri, May 15, 2020 at 02:57:01PM +0200, Greg KH wrote:
> On Fri, May 15, 2020 at 06:19:45PM +0530, Siddharth Chandrasekaran wrote:
> > Please ignore this patch set, I accidentally added another patch I was
> > working on. Will send v2 with the right patches.
>
> What patch set? I see nothing in this email, so I have no idea what you
> are referring to :(
Apologies! Looks like my email thread was broken. I was referring to
the thread here: https://lkml.org/lkml/2020/5/14/1326 with subject:
"[PATCH] Backport security fixe to 4.9 and 4.4 stable trees"
The corrected version (v2) of this patch should have reached you
(hopefully) with the subject:
"[PATCH v2] Backport xfs security fix to 4.9 and 4.4 stable trees"
Thanks!
-- Sid.
next prev parent reply other threads:[~2020-05-15 13:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 20:55 [PATCH] Backport security fixe to 4.9 and 4.4 stable trees Siddharth Chandrasekaran
2020-05-14 20:55 ` [PATCH v4.9] xfs: More robust inode extent count validation Siddharth Chandrasekaran
2020-05-14 20:55 ` [PATCH v4.4] xfs: validate cached inodes are free when allocated Siddharth Chandrasekaran
2020-05-15 12:49 ` [PATCH] Backport security fixe to 4.9 and 4.4 stable trees Siddharth Chandrasekaran
2020-05-15 12:57 ` Greg KH
2020-05-15 13:29 ` Siddharth Chandrasekaran [this message]
2020-05-15 13:40 ` Greg KH
2020-05-15 13:52 ` Steven Rostedt
2020-05-15 14:31 ` Greg KH
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=20200515132943.GA97579@csiddharth-a01.vmware.com \
--to=siddharth@embedjournal.com \
--cc=csiddharth@vmware.com \
--cc=darrick.wong@oracle.com \
--cc=dchinner@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srivatsab@vmware.com \
--cc=srostedt@vmware.com \
--cc=stable@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 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.