All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Harsh Shandilya <harsh@prjkt.io>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 3/3] ext4: don't allow r/w mounts if metadata blocks overlap the superblock
Date: Sat, 21 Apr 2018 16:07:44 -0400	[thread overview]
Message-ID: <20180421200744.GB2984@thunk.org> (raw)
In-Reply-To: <20180421122927.19842-1-harsh@prjkt.io>

On Sat, Apr 21, 2018 at 05:59:27PM +0530, Harsh Shandilya wrote:
> From: Theodore Ts'o <tytso@mit.edu>
> 
> Commit 18db4b4e6fc31eda838dd1c1296d67dbcb3dc957 upstream.

Thanks for resending with the upstream commit.  Could you include in
the future the kernel version the backport is meant for in the subject
line, e.g:

[PATCH 3.18.y 3/3] ext4: don't allow r/w mounts if metadata blocks

or 

[PATCH 4.9.y 3/3] ext4: don't allow r/w mounts if metadata blocks

Thanks!!

					- Ted

  reply	other threads:[~2018-04-21 20:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-20 22:26 [PATCH 0/4] 4.17-rc1 stable tagged ext4 patches for 3.18.y Harsh Shandilya
2018-04-20 22:26 ` [PATCH 1/4] ext4: add validity checks for bitmap block numbers Harsh Shandilya
2018-04-21 12:28   ` [PATCH 1/3] " Harsh Shandilya
2018-04-20 22:26 ` [PATCH 2/4] ext4: fail ext4_iget for root directory if unallocated Harsh Shandilya
2018-04-21 12:28   ` [PATCH 2/3] " Harsh Shandilya
2018-04-20 22:26 ` [PATCH 3/4] ext4: don't allow r/w mounts if metadata blocks overlap the superblock Harsh Shandilya
2018-04-21 12:29   ` [PATCH 3/3] " Harsh Shandilya
2018-04-21 20:07     ` Theodore Y. Ts'o [this message]
2018-04-22  2:30       ` Harsh Shandilya
2018-04-22  4:01         ` Theodore Y. Ts'o
2018-04-22  4:04           ` Harsh Shandilya
2018-04-20 22:26 ` [PATCH 4/4] ext4: force revalidation of directory pointer after seekdir(2) Harsh Shandilya
2018-04-20 23:23 ` [PATCH 0/4] 4.17-rc1 stable tagged ext4 patches for 3.18.y Harsh Shandilya
2018-04-21 12:21 ` [PATCH 0/3] " Harsh Shandilya

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=20180421200744.GB2984@thunk.org \
    --to=tytso@mit.edu \
    --cc=harsh@prjkt.io \
    --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 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.