The patch titled Subject: mm/mmu_notifier: init notifier if necessary has been added to the -mm tree. Its filename is mm-mmu_notifier-init-notifier-if-necessary-v2.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: Gavin Shan <shangw@xxxxxxxxxxxxxxxxxx> Subject: mm/mmu_notifier: init notifier if necessary v2: Use GFP_KERNEL instead of GFP_ATOMIC when allocating the MMU notifier_mm as Andrew suggested. Signed-off-by: Gavin Shan <shangw@xxxxxxxxxxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- mm/mmu_notifier.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff -puN mm/mmu_notifier.c~mm-mmu_notifier-init-notifier-if-necessary-v2 mm/mmu_notifier.c --- a/mm/mmu_notifier.c~mm-mmu_notifier-init-notifier-if-necessary-v2 +++ a/mm/mmu_notifier.c @@ -215,7 +215,7 @@ static int do_mmu_notifier_register(stru if (!mm_has_notifiers(mm)) { mmu_notifier_mm = kmalloc(sizeof(struct mmu_notifier_mm), - GFP_ATOMIC); + GFP_KERNEL); if (unlikely(!mmu_notifier_mm)) { ret = -ENOMEM; goto out_of_mem; _ Patches currently in -mm which might be from shangw@xxxxxxxxxxxxxxxxxx are mm-slab-remove-duplicate-check.patch mm-mmu_notifier-init-notifier-if-necessary.patch mm-mmu_notifier-init-notifier-if-necessary-v2.patch mm-vmscan-fix-error-number-for-failed-kthread.patch -- To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html