linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Sasha Levin <Alexander.Levin@microsoft.com>
Cc: Ext4 Developers List <linux-ext4@vger.kernel.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] ext4: protect i_disksize update by i_data_sem in direct write path
Date: Fri, 30 Mar 2018 14:14:02 -0400	[thread overview]
Message-ID: <20180330181402.GC9300@thunk.org> (raw)
In-Reply-To: <DM5PR2101MB103262C4DC678FEC128E851BFBA10@DM5PR2101MB1032.namprd21.prod.outlook.com>

On Fri, Mar 30, 2018 at 04:16:10PM +0000, Sasha Levin wrote:
> 
> Here's a mail that would be sent as a result of an autoselection. It
> will note the "score" of the patch, and will run the same tests we
> do for patches tagged for stable.
> 
> As before, please let me know your thoughts on this. Thanks!
> ...
> 
> Please let us know if you'd like to have this patch included in a stable tree.

This patch is in the ext4 tree but has not been integrated into the
mainline kernel.  It will be shortly, once the merge window opens.

How are patches selected for potential autoselection?  If they are in
linux-ext but not yet in mainline, I would assume this would be a
reason not to select it, no?

Regards,

					- Ted

      reply	other threads:[~2018-03-30 18:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180312152156.14034-2-guaneryu@gmail.com>
2018-03-30 16:16 ` [PATCH] ext4: protect i_disksize update by i_data_sem in direct write path Sasha Levin
2018-03-30 18:14   ` Theodore Y. Ts'o [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=20180330181402.GC9300@thunk.org \
    --to=tytso@mit.edu \
    --cc=Alexander.Levin@microsoft.com \
    --cc=linux-ext4@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).