From: akpm@linux-foundation.org
To: akpm@linux-foundation.org, mm-commits@vger.kernel.org
Subject: + linux-next-rejects.patch added to -mm tree
Date: Tue, 20 Jun 2017 11:28:17 -0700 [thread overview]
Message-ID: <20170620182817.rrHpMbF4b%akpm@linux-foundation.org> (raw)
The patch titled
Subject: linux-next-rejects
has been added to the -mm tree. Its filename is
linux-next-rejects.patch
This patch should soon appear at
http://ozlabs.org/~akpm/mmots/broken-out/linux-next-rejects.patch
and later at
http://ozlabs.org/~akpm/mmotm/broken-out/linux-next-rejects.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
------------------------------------------------------
From: Andrew Morton <akpm@linux-foundation.org>
Subject: linux-next-rejects
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
diff -puN include/linux/ipc.h~linux-next-rejects include/linux/ipc.h
--- a/include/linux/ipc.h~linux-next-rejects
+++ a/include/linux/ipc.h
@@ -23,6 +23,6 @@ struct kern_ipc_perm {
struct rcu_head rcu;
atomic_t refcount;
-} ____cacheline_aligned_in_smp;
+} ____cacheline_aligned_in_smp __randomize_layout;
#endif /* _LINUX_IPC_H */
diff -puN include/linux/sem.h~linux-next-rejects include/linux/sem.h
--- a/include/linux/sem.h~linux-next-rejects
+++ a/include/linux/sem.h
@@ -41,7 +41,7 @@ struct sem_array {
unsigned int use_global_lock;/* >0: global lock required */
struct sem sems[];
-};
+} __randomize_layout;
#ifdef CONFIG_SYSVIPC
_
Patches currently in -mm which might be from akpm@linux-foundation.org are
i-need-old-gcc.patch
arm-arch-arm-include-asm-pageh-needs-personalityh.patch
ocfs2-old-mle-put-and-release-after-the-function-dlm_add_migration_mle-called-fix.patch
ocfs2-dlm-optimization-of-code-while-free-dead-node-locks-checkpatch-fixes.patch
powerpc-64s-implement-arch-specific-hardlockup-watchdog-checkpatch-fixes.patch
mm.patch
mm-slub-wrap-cpu_slab-partial-in-config_slub_cpu_partial-fix.patch
swap-add-block-io-poll-in-swapin-path-checkpatch-fixes.patch
mm-oom_kill-count-global-and-memory-cgroup-oom-kills-fix.patch
mm-oom_kill-count-global-and-memory-cgroup-oom-kills-fix-fix.patch
mm-swap-sort-swap-entries-before-free-fix.patch
mm-vmscan-avoid-thrashing-anon-lru-when-free-file-is-low-fix.patch
mm-hwpoison-dissolve-in-use-hugepage-in-unrecoverable-memory-error-fix.patch
mm-hugetlb-warn-the-user-when-issues-arise-on-boot-due-to-hugepages-fix.patch
mm-improve-readability-of-transparent_hugepage_enabled-fix.patch
mm-improve-readability-of-transparent_hugepage_enabled-fix-fix.patch
hugetlb-memory_hotplug-prefer-to-use-reserved-pages-for-migration-fix.patch
signal-avoid-undefined-behaviour-in-kill_something_info-fix.patch
kernel-reboot-add-devm_register_reboot_notifier-fix.patch
fault-inject-support-systematic-fault-injection-fix.patch
linux-next-rejects.patch
linux-next-git-rejects.patch
kernel-forkc-export-kernel_thread-to-modules.patch
slab-leaks3-default-y.patch
next reply other threads:[~2017-06-20 18:28 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-20 18:28 akpm [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-04-08 17:43 + linux-next-rejects.patch added to -mm tree Andrew Morton
2022-03-28 18:46 Andrew Morton
2022-02-03 21:53 akpm
2021-12-03 17:31 akpm
2021-10-07 18:12 akpm
2021-07-27 20:07 akpm
2021-06-01 1:46 akpm
2021-03-30 0:48 akpm
2021-03-18 23:47 akpm
2021-03-11 18:51 akpm
2021-03-08 18:34 akpm
2020-12-18 23:15 akpm
2020-11-10 18:13 akpm
2020-09-03 22:00 akpm
2020-08-12 1:29 incoming Andrew Morton
2020-08-14 3:22 ` + linux-next-rejects.patch added to -mm tree Andrew Morton
2020-07-03 5:16 akpm
2020-06-09 4:29 incoming Andrew Morton
2020-06-09 4:44 ` + linux-next-rejects.patch added to -mm tree Andrew Morton
2020-06-08 5:49 akpm
2020-04-28 21:27 akpm
2020-02-19 19:15 akpm
2020-02-11 21:12 akpm
2020-01-09 22:46 akpm
2018-02-06 19:43 akpm
2017-09-25 20:57 akpm
2017-07-28 21:33 akpm
2017-06-15 23:27 akpm
2017-01-06 20:53 akpm
2016-11-14 20:01 akpm
2016-09-09 18:31 akpm
2016-07-29 18:50 akpm
2016-04-22 17:51 akpm
2016-04-01 18:54 akpm
2016-02-16 18:48 akpm
2015-12-05 1:09 akpm
2015-09-30 22:16 akpm
2015-07-08 0:24 akpm
2015-04-30 19:58 akpm
2015-03-16 18:02 akpm
2015-02-24 0:45 akpm
2015-02-12 19:34 akpm
2015-01-21 21:26 akpm
2014-11-05 20:41 akpm
2014-09-12 19:56 akpm
2014-07-24 20:43 akpm
2014-05-20 18:14 akpm
2014-04-10 23:53 akpm
2014-04-07 22:48 akpm
2014-03-12 19:05 akpm
2014-02-13 20:59 akpm
2014-02-10 20:31 akpm
2013-11-21 23:02 akpm
2013-10-29 21:35 akpm
2013-10-11 21:26 akpm
2013-09-26 0:29 akpm
2013-04-30 22:36 akpm
2013-04-29 23:38 akpm
2013-03-13 19:46 akpm
2012-12-18 22:06 akpm
2012-12-12 22:20 akpm
2012-11-14 1:20 akpm
2012-05-29 22:38 akpm
2012-04-04 19:43 akpm
2011-07-21 19:10 akpm
2011-05-25 4:02 akpm
2011-03-21 22:50 akpm
2011-02-09 21:58 akpm
2011-01-20 22:47 akpm
2011-01-13 1:20 akpm
2010-03-05 22:06 akpm
2009-03-12 19:59 akpm
2009-03-02 19:17 akpm
2009-02-13 23:49 akpm
2008-10-29 0:37 akpm
2008-07-24 23:16 akpm
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=20170620182817.rrHpMbF4b%akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@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