From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Jan Kara <jack@suse.cz>
To: <linux-fsdevel@vger.kernel.org>
Cc: Ted Tso <tytso@mit.edu>, Martijn Coenen <maco@android.com>
Cc: stable@vger.kernel.org
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 1/3] writeback: Avoid skipping inode writeback
Date: Fri, 05 Jun 2020 14:11:00 +0000 [thread overview]
Message-ID: <20200605141100.EF8EC20820@mail.kernel.org> (raw)
In-Reply-To: <20200601091904.4786-1-jack@suse.cz>
Hi
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag
fixing commit: 0ae45f63d4ef ("vfs: add support for a lazytime mount option").
The bot has tested the following trees: v5.6.15, v5.4.43, v4.19.125, v4.14.182, v4.9.225, v4.4.225.
v5.6.15: Build OK!
v5.4.43: Build OK!
v4.19.125: Build OK!
v4.14.182: Failed to apply! Possible dependencies:
80ea09a002bf ("vfs: factor out inode_insert5()")
c2b6d621c4ff ("new primitive: discard_new_inode()")
v4.9.225: Failed to apply! Possible dependencies:
09d8b586731b ("ovl: move __upperdentry to ovl_inode")
13c72075ac9f ("ovl: move impure to ovl_inode")
2aff4534b6c4 ("ovl: check lower existence when removing")
2b8c30e9ef14 ("ovl: use d_is_dir()")
32a3d848eb91 ("ovl: clean up kstat usage")
370e55ace59c ("ovl: rename: simplify handling of lower/merged directory")
38e813db61c3 ("ovl: get rid of PURE type")
3ee23ff1025a ("ovl: check lower existence of rename target")
42f269b92540 ("ovl: rearrange code in ovl_copy_up_locked()")
5cf5b477f0ca ("ovl: opaque cleanup")
6c02cb59e6fe ("ovl: rename ovl_rename2() to ovl_rename()")
804032fabb3b ("ovl: don't check rename to self")
80ea09a002bf ("vfs: factor out inode_insert5()")
8ee6059c58ea ("ovl: simplify lookup")
a6c606551141 ("ovl: redirect on rename-dir")
ad0af7104dad ("vfs: introduce inode 'inuse' lock")
bbb1e54dd53c ("ovl: split super.c")
c2b6d621c4ff ("new primitive: discard_new_inode()")
c412ce498396 ("ovl: add ovl_dentry_is_whiteout()")
ca4c8a3a8000 ("ovl: treat special files like a regular fs")
d8514d8edb5b ("ovl: copy up regular file using O_TMPFILE")
v4.4.225: Failed to apply! Possible dependencies:
09d8b586731b ("ovl: move __upperdentry to ovl_inode")
1175b6b8d963 ("ovl: do operations on underlying file system in mounter's context")
13c72075ac9f ("ovl: move impure to ovl_inode")
2864f3014242 ("iget_locked et.al.: make sure we don't return bad inodes")
32a3d848eb91 ("ovl: clean up kstat usage")
38b256973ea9 ("ovl: handle umask and posix_acl_default correctly on creation")
42f269b92540 ("ovl: rearrange code in ovl_copy_up_locked()")
6b2553918d8b ("replace ->follow_link() with new method that could stay in RCU mode")
80ea09a002bf ("vfs: factor out inode_insert5()")
aa80deab33a8 ("namei: page_getlink() and page_follow_link_light() are the same thing")
ad0af7104dad ("vfs: introduce inode 'inuse' lock")
bb0d2b8ad296 ("ovl: fix sgid on directory")
c2b6d621c4ff ("new primitive: discard_new_inode()")
d6335d77a762 ("security: Make inode argument of inode_getsecid non-const")
d8514d8edb5b ("ovl: copy up regular file using O_TMPFILE")
d8ad8b496184 ("security, overlayfs: provide copy up security hook for unioned files")
fceef393a538 ("switch ->get_link() to delayed_call, kill ->put_link()")
NOTE: The patch will not be queued to stable trees until it is upstream.
How should we proceed with this patch?
--
Thanks
Sasha
next prev parent reply other threads:[~2020-06-05 14:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-01 9:18 [PATCH 0/3] writeback: Lazytime handling fix and cleanups Jan Kara
2020-06-01 9:18 ` [PATCH 1/3] writeback: Avoid skipping inode writeback Jan Kara
2020-06-05 14:11 ` Sasha Levin [this message]
2020-06-10 15:02 ` Christoph Hellwig
2020-06-10 15:30 ` Jan Kara
2020-06-01 9:18 ` [PATCH 2/3] writeback: Fix sync livelock due to b_dirty_time processing Jan Kara
2020-06-10 15:06 ` Christoph Hellwig
2020-06-10 15:54 ` Jan Kara
2020-06-10 15:58 ` Christoph Hellwig
2020-06-01 9:18 ` [PATCH 3/3] writeback: Drop I_DIRTY_TIME_EXPIRE Jan Kara
2020-06-10 15:11 ` Christoph Hellwig
2020-06-10 16:20 ` Jan Kara
2020-06-10 10:04 ` [PATCH 0/3] writeback: Lazytime handling fix and cleanups Jan Kara
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=20200605141100.EF8EC20820@mail.kernel.org \
--to=sashal@kernel.org \
--cc=maco@android.com \
--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 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.