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: <linux-mm@kvack.org>,
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 2/3] fs: Export generic_fadvise()
Date: Fri, 12 Jul 2019 23:55:21 +0000 [thread overview]
Message-ID: <20190712235523.3A90E20874@mail.kernel.org> (raw)
In-Reply-To: <20190711140012.1671-3-jack@suse.cz>
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.2, v5.1.17, v4.19.58, v4.14.133, v4.9.185, v4.4.185.
v5.2: Build OK!
v5.1.17: Build OK!
v4.19.58: Build OK!
v4.14.133: Failed to apply! Possible dependencies:
17ef445f9bef ("Documentation/filesystems: update documentation of file_operations")
312db1aa1dc7 ("fs: add ksys_mount() helper; remove in-kernel calls to sys_mount()")
36028d5dd711 ("fs: add ksys_p{read,write}64() helpers; remove in-kernel calls to syscalls")
3a18ef5c1b39 ("fs: add ksys_umount() helper; remove in-kernel call to sys_umount()")
3ce4a7bf6626 ("fs: add ksys_read() helper; remove in-kernel calls to sys_read()")
45cd0faae371 ("vfs: add the fadvise() file operation")
6e8b704df584 ("fs: update documentation to mention __poll_t and match the code")
70f68ee81e2e ("fs: add ksys_sync() helper; remove in-kernel calls to sys_sync()")
806cbae1228c ("fs: add ksys_sync_file_range helper(); remove in-kernel calls to syscall")
819671ff849b ("syscalls: define and explain goal to not call syscalls in the kernel")
9b32105ec6b1 ("kernel: add ksys_unshare() helper; remove in-kernel calls to sys_unshare()")
9d5b7c956b09 ("mm: add ksys_fadvise64_64() helper; remove in-kernel call to sys_fadvise64_64()")
a16fe33ab557 ("fs: add ksys_chroot() helper; remove-in kernel calls to sys_chroot()")
c7248321a3d4 ("fs: add ksys_dup{,3}() helper; remove in-kernel calls to sys_dup{,3}()")
e2aaa9f42336 ("kernel: add ksys_setsid() helper; remove in-kernel call to sys_setsid()")
e7a3e8b2edf5 ("fs: add ksys_write() helper; remove in-kernel calls to sys_write()")
edf292c76b88 ("fs: add ksys_fallocate() wrapper; remove in-kernel calls to sys_fallocate()")
v4.9.185: Failed to apply! Possible dependencies:
17ef445f9bef ("Documentation/filesystems: update documentation of file_operations")
3859a271a003 ("randstruct: Mark various structs for randomization")
45cd0faae371 ("vfs: add the fadvise() file operation")
5613fda9a503 ("sched/cputime: Convert task/group cputime to nsecs")
60f3e00d25b4 ("sysv,ipc: cacheline align kern_ipc_perm")
6e8b704df584 ("fs: update documentation to mention __poll_t and match the code")
8c8b73c4811f ("sched/cputime, powerpc: Prepare accounting structure for cputime flush on tick")
a19ff1a2cc92 ("sched/cputime, powerpc/vtime: Accumulate cputime and account only on tick/task switch")
b18b6a9cef7f ("timers: Omit POSIX timer stuff from task_struct when disabled")
baa73d9e478f ("posix-timers: Make them configurable")
c3edc4010e9d ("sched/headers: Move task_struct::signal and task_struct::sighand types and accessors into <linux/sched/signal.h>")
d69dece5f5b6 ("LSM: Add /sys/kernel/security/lsm")
f828c3d0aeba ("sched/cputime, powerpc: Migrate stolen_time field to the accounting structure")
v4.4.185: Failed to apply! Possible dependencies:
04b38d601239 ("vfs: pull btrfs clone API to vfs layer")
17ef445f9bef ("Documentation/filesystems: update documentation of file_operations")
29732938a628 ("vfs: add copy_file_range syscall and vfs helper")
3859a271a003 ("randstruct: Mark various structs for randomization")
3db11b2eecc0 ("btrfs: add .copy_file_range file operation")
45cd0faae371 ("vfs: add the fadvise() file operation")
54dbc1517237 ("vfs: hoist the btrfs deduplication ioctl to the vfs")
6e8b704df584 ("fs: update documentation to mention __poll_t and match the code")
75ba1d07fd6a ("seq/proc: modify seq_put_decimal_[u]ll to take a const char *, not char")
81243eacfa40 ("cred: simpler, 1D supplementary groups")
d79bdd52d8be ("vfs: wire up compat ioctl for CLONE/CLONE_RANGE")
f7a5f132b447 ("proc: faster /proc/*/status")
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:[~2019-07-12 23:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-11 14:00 [PATCH 0/3] xfs: Fix races between readahead and hole punching Jan Kara
2019-07-11 14:00 ` [PATCH 1/3] mm: Handle MADV_WILLNEED through vfs_fadvise() Jan Kara
2019-07-12 17:50 ` Darrick J. Wong
2019-07-12 23:55 ` Sasha Levin
2019-07-23 3:08 ` Boaz Harrosh
2019-07-11 14:00 ` [PATCH 2/3] fs: Export generic_fadvise() Jan Kara
2019-07-12 17:50 ` Darrick J. Wong
2019-07-12 23:55 ` Sasha Levin [this message]
2019-07-11 14:00 ` [PATCH 3/3] xfs: Fix stale data exposure when readahead races with hole punch Jan Kara
2019-07-11 15:28 ` Amir Goldstein
2019-07-11 15:49 ` Darrick J. Wong
2019-07-12 12:00 ` Jan Kara
2019-07-12 17:56 ` Darrick J. Wong
-- strict thread matches above, loose matches on Subject: below --
2019-08-29 13:10 [PATCH 0/3 v2] xfs: Fix races between readahead and hole punching Jan Kara
2019-08-29 13:10 ` [PATCH 2/3] fs: Export generic_fadvise() 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=20190712235523.3A90E20874@mail.kernel.org \
--to=sashal@kernel.org \
--cc=linux-mm@kvack.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).