The patch titled hugetlb-do-not-allow-pagesize-=-max_order-pool-adjustment-fix-fix has been removed from the -mm tree. Its filename was hugetlb-do-not-allow-pagesize-=-max_order-pool-adjustment-fix-fix.patch This patch was dropped because it was folded into hugetlb-do-not-allow-pagesize-=-max_order-pool-adjustment.patch The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/ ------------------------------------------------------ Subject: hugetlb-do-not-allow-pagesize-=-max_order-pool-adjustment-fix-fix From: CAI Qian <caiqian@xxxxxxxxxx> add checking in hugetlb_overcommit_handler() Cc: Andrea Arcangeli <aarcange@xxxxxxxxxx> Cc: Eric B Munson <emunson@xxxxxxxxx> Cc: Michal Hocko <mhocko@xxxxxxx> Cc: Nishanth Aravamudan <nacc@xxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- mm/hugetlb.c | 4 ++++ 1 file changed, 4 insertions(+) diff -puN mm/hugetlb.c~hugetlb-do-not-allow-pagesize-=-max_order-pool-adjustment-fix-fix mm/hugetlb.c --- a/mm/hugetlb.c~hugetlb-do-not-allow-pagesize-=-max_order-pool-adjustment-fix-fix +++ a/mm/hugetlb.c @@ -1456,6 +1456,7 @@ static ssize_t nr_overcommit_hugepages_s struct hstate *h = kobj_to_hstate(kobj, NULL); return sprintf(buf, "%lu\n", h->nr_overcommit_huge_pages); } + static ssize_t nr_overcommit_hugepages_store(struct kobject *kobj, struct kobj_attribute *attr, const char *buf, size_t count) { @@ -1942,6 +1943,9 @@ int hugetlb_overcommit_handler(struct ct if (!write) tmp = h->nr_overcommit_huge_pages; + if (write && h->order >= MAX_ORDER) + return -EINVAL; + table->data = &tmp; table->maxlen = sizeof(unsigned long); ret = proc_doulongvec_minmax(table, write, buffer, length, ppos); _ Patches currently in -mm which might be from caiqian@xxxxxxxxxx are hugetlb-check-the-return-value-of-string-conversion-in-sysctl-handler.patch hugetlb-do-not-allow-pagesize-=-max_order-pool-adjustment.patch hugetlb-fix-handling-of-parse-errors-in-sysfs.patch ksm-drain-pagevecs-to-lru.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