From: Greg KH <gregkh@linuxfoundation.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Siddharth Chandrasekaran <siddharth@embedjournal.com>,
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 16:31:27 +0200 [thread overview]
Message-ID: <20200515143127.GA2464197@kroah.com> (raw)
In-Reply-To: <20200515095216.79fccd40@gandalf.local.home>
On Fri, May 15, 2020 at 09:52:16AM -0400, Steven Rostedt wrote:
> On Fri, 15 May 2020 15:40:09 +0200
> Greg KH <gregkh@linuxfoundation.org> wrote:
>
> > >
> > > "[PATCH v2] Backport xfs security fix to 4.9 and 4.4 stable trees"
> >
> > Sorry, I see no such email in my staging patch queue.
> >
> > Do you have a link to the series on lore.kernel.org? lkml.org is a mess
> > and not under our control.
>
> That's because it Cc'd stable@kernel.org and not stable@vger.kernel.org.
>
> Should Siddharth resend?
Yes, stable@kernel.org is a direct path to /dev/null on the kernel.org
mail server.
thanks,
greg k-h
prev parent reply other threads:[~2020-05-15 14:31 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
2020-05-15 13:40 ` Greg KH
2020-05-15 13:52 ` Steven Rostedt
2020-05-15 14:31 ` Greg KH [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=20200515143127.GA2464197@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=csiddharth@vmware.com \
--cc=darrick.wong@oracle.com \
--cc=dchinner@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=siddharth@embedjournal.com \
--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.