All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Mikulas Patocka <mpatocka@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>, Jan Kara <jack@suse.cz>
Cc: Jann Horn <jannh@google.com>, Christoph Hellwig <hch@lst.de>
Cc: stable@vger.kernel.org
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 1/2] ext2: don't update mtime on COW faults
Date: Mon, 07 Sep 2020 15:03:38 +0000	[thread overview]
Message-ID: <20200907150339.0D2782137B@mail.kernel.org> (raw)
In-Reply-To: <alpine.LRH.2.02.2009050811200.12419@file01.intranet.prod.int.rdu2.redhat.com>

Hi

[This is an automated email]

This commit has been processed because it contains a -stable tag.
The stable tag indicates that it's relevant for the following trees: all

The bot has tested the following trees: v5.8.7, v5.4.63, v4.19.143, v4.14.196, v4.9.235, v4.4.235.

v5.8.7: Build OK!
v5.4.63: Build OK!
v4.19.143: Build OK!
v4.14.196: Failed to apply! Possible dependencies:
    06856938112b ("fs: ext2: Adding new return type vm_fault_t")
    1b5a1cb21e0c ("dax: Inline dax_insert_mapping() into the callsite")
    31a6f1a6e5a4 ("dax: Simplify arguments of dax_insert_mapping()")
    5e161e4066d3 ("dax: Factor out getting of pfn out of iomap")
    9a0dd4225143 ("dax: Allow dax_iomap_fault() to return pfn")
    a0987ad5c576 ("dax: Create local variable for VMA in dax_iomap_pte_fault()")
    aaa422c4c3f6 ("fs, dax: unify IOMAP_F_DIRTY read vs write handling policy in the dax core")
    c0b246259792 ("dax: pass detailed error code from dax_iomap_fault()")
    caa51d26f85c ("dax, iomap: Add support for synchronous faults")
    cec04e8c825e ("dax: Fix comment describing dax_iomap_fault()")
    d2c43ef13327 ("dax: Create local variable for vmf->flags & FAULT_FLAG_WRITE test")
    f5b7b74876cf ("dax: Allow tuning whether dax_insert_mapping_entry() dirties entry")

v4.9.235: Failed to apply! Possible dependencies:
    024b6a63138c ("gpu: drm: gma500: Use vma_pages()")
    11bac8000449 ("mm, fs: reduce fault, page_mkwrite, and pfn_mkwrite to take only vmf")
    1a29d85eb0f1 ("mm: use vmf->address instead of of vmf->virtual_address")
    82b0f8c39a38 ("mm: join struct fault_env and vm_fault")

v4.4.235: Failed to apply! Possible dependencies:
    11bac8000449 ("mm, fs: reduce fault, page_mkwrite, and pfn_mkwrite to take only vmf")
    366baf28ee3f ("KVM: PPC: Use RCU for arch.spapr_tce_tables")
    462ee11e58c9 ("KVM: PPC: Replace SPAPR_TCE_SHIFT with IOMMU_PAGE_SHIFT_4K")
    5ee7af18642c ("KVM: PPC: Move reusable bits of H_PUT_TCE handler to helpers")
    d3695aa4f452 ("KVM: PPC: Add support for multiple-TCE hcalls")
    f8626985c7c2 ("KVM: PPC: Account TCE-containing pages in locked_vm")
    fcbb2ce67284 ("KVM: PPC: Rework H_PUT_TCE/H_GET_TCE handlers")
    fe26e52712cc ("KVM: PPC: Add @page_shift to kvmppc_spapr_tce_table")


NOTE: The patch will not be queued to stable trees until it is upstream.

How should we proceed with this patch?

-- 
Thanks
Sasha

  parent reply	other threads:[~2020-09-07 15:09 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-03 19:24 a crash when running strace from persistent memory Mikulas Patocka
2020-09-03 19:24 ` Mikulas Patocka
2020-09-03 19:55 ` Linus Torvalds
2020-09-03 19:55   ` Linus Torvalds
2020-09-04  8:08   ` Mikulas Patocka
2020-09-04  8:08     ` Mikulas Patocka
2020-09-04 17:11     ` Linus Torvalds
2020-09-04 17:11       ` Linus Torvalds
2020-09-04 16:21 ` make misbehavior on ext2 in dax mode (was: a crash when running strace from persistent memory) Mikulas Patocka
2020-09-04 16:21   ` Mikulas Patocka
2020-09-05 12:11   ` Mikulas Patocka
2020-09-05 12:11     ` Mikulas Patocka
2020-09-05 12:12     ` [PATCH 1/2] ext2: don't update mtime on COW faults Mikulas Patocka
2020-09-05 12:12       ` Mikulas Patocka
2020-09-07  9:00       ` Jan Kara
2020-09-07  9:00         ` Jan Kara
2020-09-07 15:03       ` Sasha Levin [this message]
2020-09-05 12:13     ` [PATCH 2/2] xfs: " Mikulas Patocka
2020-09-05 12:13       ` Mikulas Patocka
2020-09-05 15:36       ` Darrick J. Wong
2020-09-05 15:36         ` Darrick J. Wong
2020-09-05 17:02         ` Mikulas Patocka
2020-09-05 17:02           ` Mikulas Patocka
2020-09-10  6:06           ` Darrick J. Wong
2020-09-10  6:06             ` Darrick J. Wong
2020-09-11 16:41             ` Mikulas Patocka
2020-09-11 16:41               ` Mikulas Patocka
2020-09-05 16:47       ` Linus Torvalds
2020-09-05 16:47         ` Linus Torvalds
2020-09-05 17:03         ` Linus Torvalds
2020-09-05 17:03           ` Linus Torvalds
2020-09-07  8:59           ` Jan Kara
2020-09-07  8:59             ` Jan Kara
2020-09-05 17:04         ` [PATCH 2/2 v2] " Mikulas Patocka
2020-09-05 17:04           ` Mikulas Patocka
2020-09-07  6:47       ` [PATCH 2/2] " Christoph Hellwig
2020-09-07  6:47         ` Christoph Hellwig

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=20200907150339.0D2782137B@mail.kernel.org \
    --to=sashal@kernel.org \
    --cc=hch@lst.de \
    --cc=jannh@google.com \
    /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.