From: Jeremy Cline <jcline@redhat.com>
To: "Theodore Y. Ts'o" <tytso@mit.edu>,
Andreas Dilger <adilger.kernel@dilger.ca>,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
Josh Poimboeuf <jpoimboe@redhat.com>,
stable@vger.kernel.org
Subject: Re: [PATCH v2] ext4: mballoc: Fix spectre gadget in ext4_mb_regular_allocator
Date: Mon, 30 Jul 2018 14:46:59 -0400 [thread overview]
Message-ID: <3f954645-e6b5-55d8-0ccd-2d1dd5ddb80e@redhat.com> (raw)
In-Reply-To: <20180730183615.GU21725@thunk.org>
Hi Ted,
On 07/30/2018 02:36 PM, Theodore Y. Ts'o wrote:
> Hey Jeremy,
>
> I think you are also going to be changing the 1/3 patch from the
> original patch series that this was part of. That's correct, right?
>
> It would be easier for me if you could simply make all of the
> revisions you plan to make for the patch series, and then upload a
> full v2 of the entire patch series.
>
> Right now I've mentally marked the entire patch series as "waiting
> forh v2". So when you send a V2 version of individual patch out of
> that series, it leaves things unclear when/if you plan to update any
> of other patches in the series.
I dropped patch 1/3 and 2/3 from the original series because they can
both be covered by some sanitation in fs/quota/quota.c, so the this is
only patch from the v1 series that should be applied.
Sorry for not being more clear!
Cheers,
Jeremy
next prev parent reply other threads:[~2018-07-30 18:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-30 18:07 [PATCH v2] ext4: mballoc: Fix spectre gadget in ext4_mb_regular_allocator Jeremy Cline
2018-07-30 18:36 ` Theodore Y. Ts'o
2018-07-30 18:46 ` Jeremy Cline [this message]
2018-07-30 19:38 ` Theodore Y. Ts'o
2018-07-30 18:54 ` Josh Poimboeuf
2018-08-02 4:06 ` Theodore Y. Ts'o
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=3f954645-e6b5-55d8-0ccd-2d1dd5ddb80e@redhat.com \
--to=jcline@redhat.com \
--cc=adilger.kernel@dilger.ca \
--cc=jpoimboe@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tytso@mit.edu \
/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).