From: akpm@linux-foundation.org
To: akpm@linux-foundation.org, brookxu@tencent.com,
hannes@cmpxchg.org, kirill.shutemov@linux.intel.com,
mhocko@suse.com, mm-commits@vger.kernel.org,
vdavydov.dev@gmail.com
Subject: [folded-merged] memcg-fix-null-pointer-dereference-in-__mem_cgroup_usage_unregister_event-fix.patch removed from -mm tree
Date: Sat, 21 Mar 2020 18:15:19 -0700 [thread overview]
Message-ID: <20200322011519.7AzvLRMOj%akpm@linux-foundation.org> (raw)
The patch titled
Subject: memcg-fix-null-pointer-dereference-in-__mem_cgroup_usage_unregister_event-fix
has been removed from the -mm tree. Its filename was
memcg-fix-null-pointer-dereference-in-__mem_cgroup_usage_unregister_event-fix.patch
This patch was dropped because it was folded into memcg-fix-null-pointer-dereference-in-__mem_cgroup_usage_unregister_event.patch
------------------------------------------------------
From: Andrew Morton <akpm@linux-foundation.org>
Subject: memcg-fix-null-pointer-dereference-in-__mem_cgroup_usage_unregister_event-fix
fix comment, per Kirill
Cc: Chunguang Xu <brookxu@tencent.com>
Cc: Johannes Weiner <hannes@cmpxchg.org>
Cc: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
Cc: Michal Hocko <mhocko@suse.com>
Cc: Vladimir Davydov <vdavydov.dev@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/memcontrol.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/mm/memcontrol.c~memcg-fix-null-pointer-dereference-in-__mem_cgroup_usage_unregister_event-fix
+++ a/mm/memcontrol.c
@@ -4068,7 +4068,7 @@ static void __mem_cgroup_usage_unregiste
new = thresholds->spare;
- /* If items related to eventfd have been cleared, nothing to do */
+ /* If no items related to eventfd have been cleared, nothing to do */
if (!entries)
goto unlock;
_
Patches currently in -mm which might be from akpm@linux-foundation.org are
memcg-fix-null-pointer-dereference-in-__mem_cgroup_usage_unregister_event.patch
mm-hotplug-fix-hot-remove-failure-in-sparsememvmemmap-case-fix.patch
drivers-infiniband-sw-siw-siw_qp_rxc-suppress-uninitialized-var-warning.patch
drivers-tty-serial-sh-scic-suppress-uninitialized-var-warning.patch
mm.patch
mm-gup-track-foll_pin-pages-fix-2-fix.patch
mm-swap-make-page_evictable-inline-fix.patch
memcg-optimize-memorynuma_stat-like-memorystat-fix.patch
selftest-add-mremap_dontunmap-selftest-fix.patch
selftest-add-mremap_dontunmap-selftest-v7-checkpatch-fixes.patch
hugetlb_cgroup-add-reservation-accounting-for-private-mappings-fix.patch
hugetlb_cgroup-add-accounting-for-shared-mappings-fix.patch
mm-hugetlbc-fix-printk-format-warning-for-32-bit-phys_addr_t-fix.patch
mm-migratec-migrate-pg_readahead-flag-fix.patch
hv_balloon-dont-check-for-memhp_auto_online-manually-fix.patch
proc-faster-open-read-close-with-permanent-files-checkpatch-fixes.patch
linux-next-rejects.patch
linux-next-fix.patch
linux-next-git-rejects.patch
mm-add-vm_insert_pages-fix.patch
net-zerocopy-use-vm_insert_pages-for-tcp-rcv-zerocopy-fix.patch
seq_read-info-message-about-buggy-next-functions-fix.patch
drivers-tty-serial-sh-scic-suppress-warning.patch
kernel-forkc-export-kernel_thread-to-modules.patch
reply other threads:[~2020-03-22 1:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200322011519.7AzvLRMOj%akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=brookxu@tencent.com \
--cc=hannes@cmpxchg.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=mm-commits@vger.kernel.org \
--cc=vdavydov.dev@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox