incoming
Subsystems (10)
Andrew Morton
maintainer21 patches, based on c741e49150dbb0c0aebe234389f4aa8b47958fa8.
Subsystems affected by this patch series:
mm/mlock
MAINTAINERS
mailmap
mm/pagecache
mm/damon
mm/slub
mm/memcg
mm/hugetlb
mm/pagecache
Subsystem: mm/mlock
Drew DeVault <[email protected]>:
Increase default MLOCK_LIMIT to 8 MiB
Subsystem: MAINTAINERS
Dave Young <[email protected]>:
MAINTAINERS: update kdump maintainers
Subsystem: mailmap
Guo Ren <[email protected]>:
mailmap: update email address for Guo Ren
Subsystem: mm/pagecache
"Matthew Wilcox (Oracle)" <[email protected]>:
filemap: remove PageHWPoison check from next_uptodate_page()
Subsystem: mm/damon
SeongJae Park <[email protected]>:
Patch series "mm/damon: Fix fake /proc/loadavg reports", v3:
timers: implement usleep_idle_range()
mm/damon/core: fix fake load reports due to uninterruptible sleeps
Patch series "mm/damon: Trivial fixups and improvements":
mm/damon/core: use better timer mechanisms selection threshold mm/damon/dbgfs: remove an unnecessary error message mm/damon/core: remove unnecessary error messages mm/damon/vaddr: remove an unnecessary warning message mm/damon/vaddr-test: split a test function having >1024 bytes frame size mm/damon/vaddr-test: remove unnecessary variables selftests/damon: skip test if DAMON is running selftests/damon: test DAMON enabling with empty target_ids case selftests/damon: test wrong DAMOS condition ranges input selftests/damon: test debugfs file reads/writes with huge count selftests/damon: split test cases
Subsystem: mm/slub
Gerald Schaefer <[email protected]>:
mm/slub: fix endianness bug for alloc/free_traces attributes
Subsystem: mm/memcg
Waiman Long <[email protected]>:
mm/memcg: relocate mod_objcg_mlstate(), get_obj_stock() and put_obj_stock()
Subsystem: mm/hugetlb
Zhenguo Yao <[email protected]>:
hugetlbfs: fix issue of preallocation of gigantic pages can't work
Subsystem: mm/pagecache
Manjong Lee <[email protected]>:
mm: bdi: initialize bdi_min_ratio when bdi is unregistered
.mailmap | 2 MAINTAINERS | 2 include/linux/delay.h | 14 include/uapi/linux/resource.h | 13 kernel/time/timer.c | 16 - mm/backing-dev.c | 7 mm/damon/core.c | 20 - mm/damon/dbgfs.c | 4 mm/damon/vaddr-test.h | 85 ++--- mm/damon/vaddr.c | 1 mm/filemap.c | 2 mm/hugetlb.c | 2 mm/memcontrol.c | 106 +++---- mm/slub.c | 15 - tools/testing/selftests/damon/.gitignore | 2 tools/testing/selftests/damon/Makefile | 7 tools/testing/selftests/damon/_debugfs_common.sh | 52 +++ tools/testing/selftests/damon/debugfs_attrs.sh | 149 ++-------- tools/testing/selftests/damon/debugfs_empty_targets.sh | 13 tools/testing/selftests/damon/debugfs_huge_count_read_write.sh | 22 + tools/testing/selftests/damon/debugfs_schemes.sh | 19 + tools/testing/selftests/damon/debugfs_target_ids.sh | 19 + tools/testing/selftests/damon/huge_count_read_write.c | 39 ++ 23 files changed, 363 insertions(+), 248 deletions(-)
Andrew Morton
maintainerPATCH 1/21 Increase default MLOCK_LIMIT to 8 MiB
From: Drew DeVault <[email protected]>
Subject: Increase default MLOCK_LIMIT to 8 MiB
This limit has not been updated since 2008, when it was increased to 64 KiB at the request of GnuPG. Until recently, the main use-cases for this feature were (1) preventing sensitive memory from being swapped, as in GnuPG's use-case; and (2) real-time use-cases. In the first case, little memory is called for, and in the second case, the user is generally in a position to increase it if they need more.
The introduction of IOURING_REGISTER_BUFFERS adds a third use-case:
preparing fixed buffers for high-performance I/O. This use-case will take as much of this memory as it can get, but is still limited to 64 KiB by default, which is very little. This increases the limit to 8 MB, which was chosen fairly arbitrarily as a more generous, but still conservative, default value.
It is also possible to raise this limit in userspace. This is easily done, for example, in the use-case of a network daemon: systemd, for instance, provides for this via LimitMEMLOCK in the service file; OpenRC via the rc_ulimit variables. However, there is no established userspace facility for configuring this outside of daemons: end-user applications do not presently have access to a convenient means of raising their limits.
The buck, as it were, stops with the kernel. It's much easier to address it here than it is to bring it to hundreds of distributions, and it can only realistically be relied upon to be high-enough by end-user software if it is more-or-less ubiquitous. Most distros don't change this particular rlimit from the kernel-supplied default value, so a change here will easily provide that ubiquity.
---
include/uapi/linux/resource.h | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-)
include/uapi/linux/resource.h renamed from include/uapi/linux/resource.h~increase-default-mlock_limit-to-8-mib +10 -3
@@ -66,10 +66,17 @@ struct rlimit64 {#define _STK_LIM (8*1024*1024)/* -* GPG2 wants 64kB of mlocked memory, to make sure pass phrases -* and other sensitive information are never written to disk. +* Limit the amount of locked memory by some sane default: +* root can always increase this limit if needed. +* +* The main use-cases are (1) preventing sensitive memory +* from being swapped; (2) real-time operations; (3) via +* IOURING_REGISTER_BUFFERS. +* +* The first two don't need much. The latter will take as +* much as it can get. 8MB is a reasonably sane default. */ -#define MLOCK_LIMIT ((PAGE_SIZE > 64*1024) ? PAGE_SIZE : 64*1024) +#define MLOCK_LIMIT ((PAGE_SIZE > 8*1024*1024) ? PAGE_SIZE : 8*1024*1024)/* * Due to binary compatibility, the actual resource numbers
_
Re: [patch 01/21] Increase default MLOCK_LIMIT to 8 MiB
include/uapi/linux/resource.h struct rlimit64 { · line 79
Quoted 3 lines · Andrew Morton
include/uapi/linux/resource.h renamed from include/uapi/linux/resource.h~increase-default-mlock_limit-to-8-mib +1
-1-#define MLOCK_LIMIT ((PAGE_SIZE > 64*1024) ? PAGE_SIZE : 64*1024) +#define MLOCK_LIMIT ((PAGE_SIZE > 8*1024*1024) ? PAGE_SIZE : 8*1024*1024)
I think I'll just make this
#define MLOCK_LIMIT (8*1024*1024)
because at the point where it's that big, there's no point in comparing it against PAGE_SIZE any more.
If some config has that big of a page size, all the rest of the kernel infrastructure would basically be screwed. We do a lot of core kernel allocations in one-page chunks..
Linus
Andrew Morton
maintainerPATCH 2/21 MAINTAINERS: update kdump maintainers
In reply to Andrew MortonFrom: Dave Young <[email protected]>
Subject: MAINTAINERS: update kdump maintainers
Remove myself from kdump maintainers as I have no enough time to maintain it now. But I can review patches on demand though.
---
MAINTAINERS | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
MAINTAINERS renamed from MAINTAINERS~maintainers-update-kdump-maintainers +1 -1
@@ -10279,9 +10279,9 @@ F: lib/Kconfig.kcsan F: scripts/Makefile.kcsan KDUMP -M: Dave Young <[email protected]> M: Baoquan He <[email protected]> R: Vivek Goyal <[email protected]> +R: Dave Young <[email protected]> L: [email protected] S: Maintained W: http://lse.sourceforge.net/kdump/
_
Andrew Morton
maintainerPATCH 3/21 mailmap: update email address for Guo Ren
In reply to Andrew MortonFrom: Guo Ren <[email protected]>
Subject: mailmap: update email address for Guo Ren
The [email protected] would be deprecated and use [email protected] as the main email address.
---
.mailmap | 2 ++ 1 file changed, 2 insertions(+)
.mailmap renamed from .mailmap~mailmap-update-email-address-for-guo-ren +2 -0
@@ -126,6 +126,8 @@ Greg Kroah-Hartman <[email protected]> Greg Kroah-Hartman <[email protected]> Greg Kurz <[email protected]> <[email protected]> Gregory CLEMENT <[email protected]> <[email protected]> +Guo Ren <[email protected]> <[email protected]> +Guo Ren <[email protected]> <[email protected]> Gustavo Padovan <[email protected]> Gustavo Padovan <[email protected]> Hanjun Guo <[email protected]> <[email protected]>
_
Andrew Morton
maintainerPATCH 4/21 filemap: remove PageHWPoison check from next_uptodate_page()
In reply to Andrew MortonFrom: "Matthew Wilcox (Oracle)" <[email protected]>
Subject: filemap: remove PageHWPoison check from next_uptodate_page()
Pages are individually marked as suffering from hardware poisoning. Checking that the head page is not hardware poisoned doesn't make sense; we might be after a subpage. We check each page individually before we use it, so this was an optimisation gone wrong. It will cause us to fall back to the slow path when there was no need to do that
---
mm/filemap.c | 2 -- 1 file changed, 2 deletions(-)
mm/filemap.c renamed from mm/filemap.c~filemap-remove-pagehwpoison-check-from-next_uptodate_page +0 -2
@@ -3253,8 +3253,6 @@ static struct page *next_uptodate_page(s goto skip;if (!PageUptodate (page) ||PageReadahead (page)) goto skip; -if (PageHWPoison (page)) - goto skip;if (!trylock_page (page)) goto skip;if (page->mapping != mapping)
_
Andrew Morton
maintainerPATCH 5/21 timers: implement usleep_idle_range()
In reply to Andrew MortonFrom: SeongJae Park <[email protected]>
Subject: timers: implement usleep_idle_range()
Patch series "mm/damon: Fix fake /proc/loadavg reports", v3.
This patchset fixes DAMON's fake load report issue. The first patch makes yet another variant of usleep_range() for this fix, and the second patch fixes the issue of DAMON by making it using the newly introduced function.
This patch (of 2):
Some kernel threads such as DAMON could need to repeatedly sleep in micro seconds level. Because usleep_range() sleeps in uninterruptible state, however, such threads would make /proc/loadavg reports fake load.
To help such cases, this commit implements a variant of usleep_range() called usleep_idle_range(). It is same to usleep_range() but sets the state of the current task as TASK_IDLE while sleeping.
---
include/linux/delay.h | 14 +++++++++++++- kernel/time/timer.c | 16 +++++++++------- 2 files changed, 22 insertions(+), 8 deletions(-)
include/linux/delay.h renamed from include/linux/delay.h~timers-implement-usleep_idle_range +13 -1
@@ -20,6 +20,7 @@*/ #include <linux/math.h> +#include <linux/sched.h> extern unsigned long loops_per_jiffy;
@@ -58,7 +59,18 @@ void calibrate_delay(void);void __attribute__((weak))calibration_delay_done (void );void msleep (unsigned int msecs);unsigned long msleep_interruptible (unsigned int msecs); -void usleep_range (unsigned long min,unsigned long max); +void usleep_range_state (unsigned long min,unsigned long max, +unsigned int state); + +static inline void usleep_range (unsigned long min,unsigned long max) +{ +usleep_range_state (min, max,TASK_UNINTERRUPTIBLE ); +} + +static inline void usleep_idle_range (unsigned long min,unsigned long max) +{ +usleep_range_state (min, max,TASK_IDLE ); +}static inline void ssleep (unsigned int seconds) {
kernel/time/timer.c renamed from kernel/time/timer.c~timers-implement-usleep_idle_range +9 -7
@@ -2054,26 +2054,28 @@ unsigned long msleep_interruptible(unsigEXPORT_SYMBOL (msleep_interruptible);/** -* usleep_range - Sleep for an approximate time -* @min: Minimum time in usecs to sleep -* @max: Maximum time in usecs to sleep +* usleep_range_state - Sleep for an approximate time in a given state +* @min: Minimum time in usecs to sleep +* @max: Maximum time in usecs to sleep +* @state: State of the current task that will be while sleeping * * In non-atomic context where the exact wakeup time is flexible, use -* usleep_range() instead of udelay(). The sleep improves responsiveness +* usleep_range_state() instead of udelay(). The sleep improves responsiveness * by avoiding the CPU-hogging busy-wait of udelay(), and the range reduces * power usage by allowing hrtimers to take advantage of an already- * scheduled interrupt instead of scheduling a new one just for this sleep. */ -void __sched usleep_range(unsigned long min, unsigned long max) +void __sched usleep_range_state(unsigned long min, unsigned long max, +unsigned int state) {ktime_t exp =ktime_add_us (ktime_get (), min);u64 delta = (u64)(max - min) *NSEC_PER_USEC ;for (;;) { -__set_current_state (TASK_UNINTERRUPTIBLE ); +__set_current_state (state);/* Do not return before the requested sleep time has elapsed */ if (!schedule_hrtimeout_range (&exp, delta,HRTIMER_MODE_ABS ))break ; } } -EXPORT_SYMBOL (usleep_range); +EXPORT_SYMBOL (usleep_range_state);
_
Andrew Morton
maintainerPATCH 6/21 mm/damon/core: fix fake load reports due to uninterruptible sleeps
In reply to Andrew MortonFrom: SeongJae Park <[email protected]>
Subject: mm/damon/core: fix fake load reports due to uninterruptible sleeps
Because DAMON sleeps in uninterruptible mode, /proc/loadavg reports fake load while DAMON is turned on, though it is doing nothing. This can confuse users[1]. To avoid the case, this commit makes DAMON sleeps in idle mode.
[1] https://lore.kernel.org/all/[email protected]/
---
mm/damon/core.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
mm/damon/core.c renamed from mm/damon/core.c~mm-damon-core-fix-fake-load-reports-due-to-uninterruptible-sleeps +3 -3
@@ -981,9 +981,9 @@ static unsigned long damos_wmark_wait_usstatic void kdamond_usleep (unsigned long usecs) {if (usecs >100 *1000 ) -schedule_timeout_interruptible (usecs_to_jiffies (usecs)); +schedule_timeout_idle (usecs_to_jiffies (usecs));else -usleep_range (usecs, usecs +1 ); +usleep_idle_range (usecs, usecs +1 ); }/* Returns negative error code if it's not activated but should return */
@@ -1038,7 +1038,7 @@ static int kdamond_fn(void *data) ctx->callback.after_sampling(ctx)) done = true; -usleep_range (ctx->sample_interval, ctx->sample_interval +1 ); +kdamond_usleep (ctx->sample_interval);if (ctx->primitive.check_accesses) max_nr_accesses = ctx->primitive.check_accesses (ctx);
_
Andrew Morton
maintainerPATCH 7/21 mm/damon/core: use better timer mechanisms selection threshold
In reply to Andrew MortonFrom: SeongJae Park <[email protected]>
Subject: mm/damon/core: use better timer mechanisms selection threshold
Patch series "mm/damon: Trivial fixups and improvements".
This patchset contains trivial fixups and improvements for DAMON and its kunit/kselftest tests.
This patch (of 11):
DAMON is using hrtimer if requested sleep time is <=100ms, while the suggested threshold[1] is <=20ms. This commit applies the threshold.
[1] Documentation/timers/timers-howto.rst
---
mm/damon/core.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
mm/damon/core.c renamed from mm/damon/core.c~mm-damon-core-use-better-timer-mechanisms-selection-threshold +2 -1
@@ -980,7 +980,8 @@ static unsigned long damos_wmark_wait_usstatic void kdamond_usleep (unsigned long usecs) { -if (usecs >100 *1000 ) +/* See Documentation/timers/timers-howto.rst for the thresholds */ +if (usecs >20 *USEC_PER_MSEC )schedule_timeout_idle (usecs_to_jiffies (usecs));else usleep_idle_range (usecs, usecs +1 );
_
Andrew Morton
maintainerPATCH 8/21 mm/damon/dbgfs: remove an unnecessary error message
In reply to Andrew MortonFrom: SeongJae Park <[email protected]>
Subject: mm/damon/dbgfs: remove an unnecessary error message
When wrong scheme action is requested via the debugfs interface, DAMON prints an error message. Because the function returns error code, this is not really needed. Because the code path is triggered by the user specified input, this can result in kernel log mistakenly being messy. To avoid the case, this commit removes the message.
---
mm/damon/dbgfs.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-)
mm/damon/dbgfs.c renamed from mm/damon/dbgfs.c~mm-damon-dbgfs-remove-an-unnecessary-error-message +1 -3
@@ -210,10 +210,8 @@ static struct damos **str_to_schemes(con &wmarks.low, &parsed);if (ret !=18 )break ; -if (!damos_action_valid (action)) { -pr_err ("wrong action %d\n" , action); +if (!damos_action_valid (action)) goto fail; - } pos += parsed; scheme = damon_new_scheme(min_sz, max_sz, min_nr_a, max_nr_a,
_
Andrew Morton
maintainerPATCH 9/21 mm/damon/core: remove unnecessary error messages
In reply to Andrew MortonFrom: SeongJae Park <[email protected]>
Subject: mm/damon/core: remove unnecessary error messages
DAMON core prints error messages when damon_target object creation is failed or wrong monitoring attributes are given. Because appropriate error code is returned for each case, the messages are not essential. Also, because the code path can be triggered with user-specified input, this could result in kernel log mistakenly being messy. To avoid the case, this commit removes the messages.
---
mm/damon/core.c | 11 ++--------- 1 file changed, 2 insertions(+), 9 deletions(-)
mm/damon/core.c renamed from mm/damon/core.c~mm-damon-core-remove-unnecessary-error-messages +2 -9
@@ -282,7 +282,6 @@ int damon_set_targets(struct damon_ctx *for (i =0 ; i < nr_ids; i++) { t =damon_new_target (ids[i]);if (!t) { -pr_err ("Failed to alloc damon_target\n" );/* The caller should do cleanup of the ids itself */ damon_for_each_target_safe (t, next, ctx)damon_destroy_target (t);
@@ -312,16 +311,10 @@ int damon_set_attrs(struct damon_ctx *ct unsigned long aggr_int, unsigned long primitive_upd_int, unsigned long min_nr_reg, unsigned long max_nr_reg) { - if (min_nr_reg < 3) { - pr_err("min_nr_regions (%lu) must be at least 3\n", - min_nr_reg); + if (min_nr_reg < 3) return -EINVAL; - } -if (min_nr_reg > max_nr_reg) { -pr_err ("invalid nr_regions. min (%lu) > max (%lu)\n" , - min_nr_reg, max_nr_reg); +if (min_nr_reg > max_nr_reg)return -EINVAL ; - } ctx->sample_interval = sample_int; ctx->aggr_interval = aggr_int;
_
Andrew Morton
maintainerPATCH 10/21 mm/damon/vaddr: remove an unnecessary warning message
In reply to Andrew MortonFrom: SeongJae Park <[email protected]>
Subject: mm/damon/vaddr: remove an unnecessary warning message
The DAMON virtual address space monitoring primitive prints a warning message for wrong DAMOS action. However, it is not essential as the code returns appropriate failure in the case. This commit removes the message to make the log clean.
---
mm/damon/vaddr.c | 1 - 1 file changed, 1 deletion(-)
mm/damon/vaddr.c renamed from mm/damon/vaddr.c~mm-damon-vaddr-remove-an-unnecessary-warning-message +0 -1
@@ -627,7 +627,6 @@ int damon_va_apply_scheme(struct damon_ccase DAMOS_STAT :return 0 ;default : -pr_warn ("Wrong action %d\n" , scheme->action);return -EINVAL ; }
_
Andrew Morton
maintainerPATCH 11/21 mm/damon/vaddr-test: split a test function having >1024 bytes frame size
In reply to Andrew MortonFrom: SeongJae Park <[email protected]>
Subject: mm/damon/vaddr-test: split a test function having >1024 bytes frame size
On some configuration[1], 'damon_test_split_evenly()' kunit test function has >1024 bytes frame size, so below build warning is triggered:
CC mm/damon/vaddr.o
In file included from mm/damon/vaddr.c:672:
mm/damon/vaddr-test.h: In function 'damon_test_split_evenly':
mm/damon/vaddr-test.h:309:1: warning: the frame size of 1064 bytes is larger than 1024 bytes [-Wframe-larger-than=]
309 | }
| ^
This commit fixes the warning by separating the common logic in the function.
[1] https://lore.kernel.org/linux-mm/[email protected]/
---
mm/damon/vaddr-test.h | 77 ++++++++++++++++++++-------------------- 1 file changed, 40 insertions(+), 37 deletions(-)
mm/damon/vaddr-test.h renamed from mm/damon/vaddr-test.h~mm-damon-vaddr-test-split-a-test-function-having-1024-bytes-frame-size +40 -37
@@ -252,59 +252,62 @@ static void damon_test_apply_three_regio new_three_regions, expected, ARRAY_SIZE(expected)); } -static void damon_test_split_evenly (struct kunit *test) +static void damon_test_split_evenly_fail (struct kunit *test, +unsigned long start,unsigned long end,unsigned int nr_pieces) { -struct damon_ctx *c =damon_new_ctx (); -struct damon_target *t; -struct damon_region *r; -unsigned long i; - -KUNIT_EXPECT_EQ (test,damon_va_evenly_split_region (NULL ,NULL ,5 ), - -EINVAL ); - - t =damon_new_target (42 ); - r =damon_new_region (0 ,100 ); -KUNIT_EXPECT_EQ (test,damon_va_evenly_split_region (t, r,0 ), -EINVAL ); +struct damon_target *t =damon_new_target (42 ); +struct damon_region *r =damon_new_region (start, end);damon_add_region (r, t); -KUNIT_EXPECT_EQ (test,damon_va_evenly_split_region (t, r,10 ),0 ); -KUNIT_EXPECT_EQ (test,damon_nr_regions (t),10u ); +KUNIT_EXPECT_EQ (test, +damon_va_evenly_split_region (t, r, nr_pieces), -EINVAL ); +KUNIT_EXPECT_EQ (test,damon_nr_regions (t),1u ); - i =0 ;damon_for_each_region (r, t) { -KUNIT_EXPECT_EQ (test, r->ar.start, i++ *10 ); -KUNIT_EXPECT_EQ (test, r->ar.end, i *10 ); +KUNIT_EXPECT_EQ (test, r->ar.start, start); +KUNIT_EXPECT_EQ (test, r->ar.end, end); } +damon_free_target (t); +} + +static void damon_test_split_evenly_succ (struct kunit *test, +unsigned long start,unsigned long end,unsigned int nr_pieces) +{ +struct damon_target *t =damon_new_target (42 ); +struct damon_region *r =damon_new_region (start, end); +unsigned long expected_width = (end - start) / nr_pieces; +unsigned long i =0 ; - t =damon_new_target (42 ); - r =damon_new_region (5 ,59 );damon_add_region (r, t); -KUNIT_EXPECT_EQ (test,damon_va_evenly_split_region (t, r,5 ),0 ); -KUNIT_EXPECT_EQ (test,damon_nr_regions (t),5u ); +KUNIT_EXPECT_EQ (test, +damon_va_evenly_split_region (t, r, nr_pieces),0 ); +KUNIT_EXPECT_EQ (test,damon_nr_regions (t), nr_pieces); - i =0 ;damon_for_each_region (r, t) { -if (i ==4 ) +if (i == nr_pieces -1 )break ; -KUNIT_EXPECT_EQ (test, r->ar.start,5 +10 * i++); -KUNIT_EXPECT_EQ (test, r->ar.end,5 +10 * i); +KUNIT_EXPECT_EQ (test, + r->ar.start, start + i++ * expected_width); +KUNIT_EXPECT_EQ (test, r->ar.end, start + i * expected_width); } -KUNIT_EXPECT_EQ (test, r->ar.start,5 +10 * i); -KUNIT_EXPECT_EQ (test, r->ar.end,59ul ); +KUNIT_EXPECT_EQ (test, r->ar.start, start + i * expected_width); +KUNIT_EXPECT_EQ (test, r->ar.end, end);damon_free_target (t); +} - t =damon_new_target (42 ); - r =damon_new_region (5 ,6 ); -damon_add_region (r, t); -KUNIT_EXPECT_EQ (test,damon_va_evenly_split_region (t, r,2 ), -EINVAL ); -KUNIT_EXPECT_EQ (test,damon_nr_regions (t),1u ); +static void damon_test_split_evenly (struct kunit *test) +{ +struct damon_ctx *c =damon_new_ctx (); + +KUNIT_EXPECT_EQ (test,damon_va_evenly_split_region (NULL ,NULL ,5 ), + -EINVAL ); + +damon_test_split_evenly_fail (test,0 ,100 ,0 ); +damon_test_split_evenly_succ (test,0 ,100 ,10 ); +damon_test_split_evenly_succ (test,5 ,59 ,5 ); +damon_test_split_evenly_fail (test,5 ,6 ,2 ); -damon_for_each_region (r, t) { -KUNIT_EXPECT_EQ (test, r->ar.start,5ul ); -KUNIT_EXPECT_EQ (test, r->ar.end,6ul ); - } -damon_free_target (t);damon_destroy_ctx (c); }
_
Andrew Morton
maintainerPATCH 12/21 mm/damon/vaddr-test: remove unnecessary variables
In reply to Andrew MortonFrom: SeongJae Park <[email protected]>
Subject: mm/damon/vaddr-test: remove unnecessary variables
A couple of test functions in DAMON virtual address space monitoring primitives implementation has unnecessary damon_ctx variables. This commit removes those.
---
mm/damon/vaddr-test.h | 8 -------- 1 file changed, 8 deletions(-)
mm/damon/vaddr-test.h renamed from mm/damon/vaddr-test.h~mm-damon-vaddr-test-remove-unnecessary-variables +0 -8
@@ -135,7 +135,6 @@ static void damon_do_test_apply_three_restruct damon_addr_range *three_regions, unsigned long *expected, int nr_expected) { - struct damon_ctx *ctx = damon_new_ctx(); struct damon_target *t;struct damon_region *r;int i;
@@ -145,7 +144,6 @@ static void damon_do_test_apply_three_re r =damon_new_region (regions[i *2 ], regions[i *2 +1 ]);damon_add_region (r, t); } -damon_add_target (ctx, t);damon_va_apply_three_regions (t, three_regions);
@@ -154,8 +152,6 @@ static void damon_do_test_apply_three_reKUNIT_EXPECT_EQ (test, r->ar.start, expected[i *2 ]);KUNIT_EXPECT_EQ (test, r->ar.end, expected[i *2 +1 ]); } - -damon_destroy_ctx (ctx); }/*
@@ -298,8 +294,6 @@ static void damon_test_split_evenly_succstatic void damon_test_split_evenly (struct kunit *test) { -struct damon_ctx *c =damon_new_ctx (); -KUNIT_EXPECT_EQ (test,damon_va_evenly_split_region (NULL ,NULL ,5 ), -EINVAL );
@@ -307,8 +301,6 @@ static void damon_test_split_evenly(strudamon_test_split_evenly_succ (test,0 ,100 ,10 );damon_test_split_evenly_succ (test,5 ,59 ,5 );damon_test_split_evenly_fail (test,5 ,6 ,2 ); - -damon_destroy_ctx (c); }static struct kunit_case damon_test_cases[] = {
_
Andrew Morton
maintainerPATCH 13/21 selftests/damon: skip test if DAMON is running
In reply to Andrew MortonFrom: SeongJae Park <[email protected]>
Subject: selftests/damon: skip test if DAMON is running
Testing the DAMON debugfs files while DAMON is running makes no sense, as any write to the debugfs files will fail. This commit makes the test be skipped in this case.
---
tools/testing/selftests/damon/debugfs_attrs.sh | 9 +++++++++ 1 file changed, 9 insertions(+)
tools/testing/selftests/damon/debugfs_attrs.sh renamed from tools/testing/selftests/damon/debugfs_attrs.sh~selftests-damon-skip-test-if-damon-is-running +9 -0
@@ -44,6 +44,15 @@ test_content() { source ./_chk_dependency.sh +ksft_skip=4 + +damon_onoff="$DBGFS/monitor_on" +if [ $(cat "$damon_onoff") = "on" ] +then + echo "monitoring is on" + exit $ksft_skip +fi + # Test attrs file # ===============
_
Andrew Morton
maintainerPATCH 14/21 selftests/damon: test DAMON enabling with empty target_ids case
In reply to Andrew MortonFrom: SeongJae Park <[email protected]>
Subject: selftests/damon: test DAMON enabling with empty target_ids case
DAMON debugfs didn't check empty targets when starting monitoring, and the issue is fixed with commit b5ca3e83ddb0 ("mm/damon/dbgfs: add adaptive_targets list check before enable monitor_on"). To avoid future regression, this commit adds a test case for that in DAMON selftests.
---
tools/testing/selftests/damon/debugfs_attrs.sh | 9 +++++++++ 1 file changed, 9 insertions(+)
tools/testing/selftests/damon/debugfs_attrs.sh renamed from tools/testing/selftests/damon/debugfs_attrs.sh~selftests-damon-test-damon-enabling-with-empty-target_ids-case +9 -0
@@ -94,4 +94,13 @@ test_write_succ "$file" "" "$orig_conten test_content "$file" "$orig_content" "" "empty input written" echo "$orig_content" > "$file" +# Test empty targets case +# ======================= + +orig_target_ids=$(cat "$DBGFS/target_ids") +echo "" > "$DBGFS/target_ids" +orig_monitor_on=$(cat "$DBGFS/monitor_on") +test_write_fail "$DBGFS/monitor_on" "on" "orig_monitor_on" "empty target ids" +echo "$orig_target_ids" > "$DBGFS/target_ids" + echo "PASS"
_
Andrew Morton
maintainerPATCH 15/21 selftests/damon: test wrong DAMOS condition ranges input
In reply to Andrew MortonFrom: SeongJae Park <[email protected]>
Subject: selftests/damon: test wrong DAMOS condition ranges input
A patch titled "mm/damon/schemes: add the validity judgment of thresholds"[1] makes DAMON debugfs interface to validate DAMON scheme inputs. This commit adds a test case for the validation logic in DAMON selftests.
---
tools/testing/selftests/damon/debugfs_attrs.sh | 2 ++ 1 file changed, 2 insertions(+)
tools/testing/selftests/damon/debugfs_attrs.sh renamed from tools/testing/selftests/damon/debugfs_attrs.sh~selftests-damon-test-wrong-damos-condition-ranges-input +2 -0
@@ -77,6 +77,8 @@ test_write_succ "$file" "1 2 3 4 5 6 4 0 test_write_fail "$file" "1 2 3 4 5 6 3 0 0 0 1 2 3 1 100 3 2 1" "$orig_content" "multi lines" test_write_succ "$file" "" "$orig_content" "disabling" +test_write_fail "$file" "2 1 2 1 10 1 3 10 1 1 1 1 1 1 1 1 2 3" \ + "$orig_content" "wrong condition ranges" echo "$orig_content" > "$file" # Test target_ids file
_
Andrew Morton
maintainerPATCH 16/21 selftests/damon: test debugfs file reads/writes with huge count
In reply to Andrew MortonFrom: SeongJae Park <[email protected]>
Subject: selftests/damon: test debugfs file reads/writes with huge count
DAMON debugfs interface users were able to trigger warning by writing some files with arbitrarily large 'count' parameter. The issue is fixed with commit db7a347b26fe ("mm/damon/dbgfs: use '__GFP_NOWARN' for user-specified size buffer allocation"). This commit adds a test case for the issue in DAMON selftests to avoid future regressions.
---
tools/testing/selftests/damon/.gitignore | 2 tools/testing/selftests/damon/Makefile | 2 tools/testing/selftests/damon/debugfs_attrs.sh | 18 ++++ tools/testing/selftests/damon/huge_count_read_write.c | 39 ++++++++++ 4 files changed, 61 insertions(+)
tools/testing/selftests/damon/debugfs_attrs.sh renamed from tools/testing/selftests/damon/debugfs_attrs.sh~selftests-damon-test-debugfs-file-reads-writes-with-huge-count +18 -0
@@ -105,4 +105,22 @@ orig_monitor_on=$(cat "$DBGFS/monitor_on test_write_fail "$DBGFS/monitor_on" "on" "orig_monitor_on" "empty target ids" echo "$orig_target_ids" > "$DBGFS/target_ids" +# Test huge count read write +# ========================== + +dmesg -C + +for file in "$DBGFS/"* +do + ./huge_count_read_write "$file" +done + +if dmesg | grep -q WARNING +then + dmesg + exit 1 +else + exit 0 +fi + echo "PASS"
tools/testing/selftests/damon/.gitignore new file +2 -0
@@ -0,0 +1,2 @@ +# SPDX-License-Identifier: GPL-2.0-only +huge_count_read_write
tools/testing/selftests/damon/huge_count_read_write.c new file +39 -0
@@ -0,0 +1,39 @@ +// SPDX-License-Identifier: GPL-2.0 +/* +* Author: SeongJae Park <[email protected]> +*/ + +#include <fcntl.h> +#include <stdlib.h> +#include <unistd.h> +#include <stdio.h> + +void write_read_with_huge_count (char *file) +{ +int filedesc =open (file,O_RDWR ); +char buf[25 ]; +int ret; + +printf ("%s %s\n" , __func__, file); +if (filedesc <0 ) { +fprintf (stderr,"failed opening %s\n" , file); +exit (1 ); + } + +write (filedesc,"" ,0xfffffffful ); +perror ("after write: " ); + ret =read (filedesc, buf,0xfffffffful ); +perror ("after read: " ); +close (filedesc); +} + +int main (int argc,char *argv[]) +{ +if (argc !=2 ) { +fprintf (stderr,"Usage: %s <file>\n" , argv[0 ]); +exit (1 ); + } +write_read_with_huge_count (argv[1 ]); + +return 0 ; +}
tools/testing/selftests/damon/Makefile renamed from tools/testing/selftests/damon/Makefile~selftests-damon-test-debugfs-file-reads-writes-with-huge-count +2 -0
@@ -1,6 +1,8 @@ # SPDX-License-Identifier: GPL-2.0 # Makefile for damon selftests +TEST_GEN_FILES += huge_count_read_write + TEST_FILES = _chk_dependency.sh TEST_PROGS = debugfs_attrs.sh
_
Andrew Morton
maintainerPATCH 17/21 selftests/damon: split test cases
In reply to Andrew MortonFrom: SeongJae Park <[email protected]>
Subject: selftests/damon: split test cases
Currently, the single test program, debugfs.sh, contains all test cases for DAMON. When one of the cases fails, finding which case is failed from the test log is not so easy, and all remaining tests will be skipped. To improve the situation, this commit splits the single program into small test programs having their own names.
---
tools/testing/selftests/damon/Makefile | 5 tools/testing/selftests/damon/_debugfs_common.sh | 52 ++++ tools/testing/selftests/damon/debugfs_attrs.sh | 111 ---------- tools/testing/selftests/damon/debugfs_empty_targets.sh | 13 + tools/testing/selftests/damon/debugfs_huge_count_read_write.sh | 22 + tools/testing/selftests/damon/debugfs_schemes.sh | 19 + tools/testing/selftests/damon/debugfs_target_ids.sh | 19 + 7 files changed, 129 insertions(+), 112 deletions(-)
tools/testing/selftests/damon/debugfs_attrs.sh renamed from tools/testing/selftests/damon/debugfs_attrs.sh~selftests-damon-split-test-cases +1 -110
@@ -1,57 +1,7 @@ #!/bin/bash # SPDX-License-Identifier: GPL-2.0 -test_write_result() { - file=$1 - content=$2 - orig_content=$3 - expect_reason=$4 - expected=$5 - - echo "$content" > "$file" - if [ $? -ne "$expected" ] - then - echo "writing $content to $file doesn't return $expected" - echo "expected because: $expect_reason" - echo "$orig_content" > "$file" - exit 1 - fi -} - -test_write_succ() { - test_write_result "$1" "$2" "$3" "$4" 0 -} - -test_write_fail() { - test_write_result "$1" "$2" "$3" "$4" 1 -} - -test_content() { - file=$1 - orig_content=$2 - expected=$3 - expect_reason=$4 - - content=$(cat "$file") - if [ "$content" != "$expected" ] - then - echo "reading $file expected $expected but $content" - echo "expected because: $expect_reason" - echo "$orig_content" > "$file" - exit 1 - fi -} - -source ./_chk_dependency.sh - -ksft_skip=4 - -damon_onoff="$DBGFS/monitor_on" -if [ $(cat "$damon_onoff") = "on" ] -then - echo "monitoring is on" - exit $ksft_skip -fi +source _debugfs_common.sh # Test attrs file # ===============
@@ -65,62 +15,3 @@ test_write_fail "$file" "1 2 3 5 4" "$or "min_nr_regions > max_nr_regions" test_content "$file" "$orig_content" "1 2 3 4 5" "successfully written" echo "$orig_content" > "$file" - -# Test schemes file -# ================= - -file="$DBGFS/schemes" -orig_content=$(cat "$file") - -test_write_succ "$file" "1 2 3 4 5 6 4 0 0 0 1 2 3 1 100 3 2 1" \ - "$orig_content" "valid input" -test_write_fail "$file" "1 2 -3 4 5 6 3 0 0 0 1 2 3 1 100 3 2 1" "$orig_content" "multi lines" -test_write_succ "$file" "" "$orig_content" "disabling" -test_write_fail "$file" "2 1 2 1 10 1 3 10 1 1 1 1 1 1 1 1 2 3" \ - "$orig_content" "wrong condition ranges" -echo "$orig_content" > "$file" - -# Test target_ids file -# ==================== - -file="$DBGFS/target_ids" -orig_content=$(cat "$file") - -test_write_succ "$file" "1 2 3 4" "$orig_content" "valid input" -test_write_succ "$file" "1 2 abc 4" "$orig_content" "still valid input" -test_content "$file" "$orig_content" "1 2" "non-integer was there" -test_write_succ "$file" "abc 2 3" "$orig_content" "the file allows wrong input" -test_content "$file" "$orig_content" "" "wrong input written" -test_write_succ "$file" "" "$orig_content" "empty input" -test_content "$file" "$orig_content" "" "empty input written" -echo "$orig_content" > "$file" - -# Test empty targets case -# ======================= - -orig_target_ids=$(cat "$DBGFS/target_ids") -echo "" > "$DBGFS/target_ids" -orig_monitor_on=$(cat "$DBGFS/monitor_on") -test_write_fail "$DBGFS/monitor_on" "on" "orig_monitor_on" "empty target ids" -echo "$orig_target_ids" > "$DBGFS/target_ids" - -# Test huge count read write -# ========================== - -dmesg -C - -for file in "$DBGFS/"* -do - ./huge_count_read_write "$file" -done - -if dmesg | grep -q WARNING -then - dmesg - exit 1 -else - exit 0 -fi - -echo "PASS"
tools/testing/selftests/damon/_debugfs_common.sh new file +52 -0
52 lines not on this page · raw message
tools/testing/selftests/damon/debugfs_empty_targets.sh new file +13 -0
@@ -0,0 +1,13 @@ +#!/bin/bash +# SPDX-License-Identifier: GPL-2.0 + +source _debugfs_common.sh + +# Test empty targets case +# ======================= + +orig_target_ids=$(cat "$DBGFS/target_ids") +echo "" > "$DBGFS/target_ids" +orig_monitor_on=$(cat "$DBGFS/monitor_on") +test_write_fail "$DBGFS/monitor_on" "on" "orig_monitor_on" "empty target ids" +echo "$orig_target_ids" > "$DBGFS/target_ids"
tools/testing/selftests/damon/debugfs_huge_count_read_write.sh new file +22 -0
@@ -0,0 +1,22 @@ +#!/bin/bash +# SPDX-License-Identifier: GPL-2.0 + +source _debugfs_common.sh + +# Test huge count read write +# ========================== + +dmesg -C + +for file in "$DBGFS/"* +do + ./huge_count_read_write "$file" +done + +if dmesg | grep -q WARNING +then + dmesg + exit 1 +else + exit 0 +fi
tools/testing/selftests/damon/debugfs_schemes.sh new file +19 -0
@@ -0,0 +1,19 @@ +#!/bin/bash +# SPDX-License-Identifier: GPL-2.0 + +source _debugfs_common.sh + +# Test schemes file +# ================= + +file="$DBGFS/schemes" +orig_content=$(cat "$file") + +test_write_succ "$file" "1 2 3 4 5 6 4 0 0 0 1 2 3 1 100 3 2 1" \ + "$orig_content" "valid input" +test_write_fail "$file" "1 2 +3 4 5 6 3 0 0 0 1 2 3 1 100 3 2 1" "$orig_content" "multi lines" +test_write_succ "$file" "" "$orig_content" "disabling" +test_write_fail "$file" "2 1 2 1 10 1 3 10 1 1 1 1 1 1 1 1 2 3" \ + "$orig_content" "wrong condition ranges" +echo "$orig_content" > "$file"
tools/testing/selftests/damon/debugfs_target_ids.sh new file +19 -0
@@ -0,0 +1,19 @@ +#!/bin/bash +# SPDX-License-Identifier: GPL-2.0 + +source _debugfs_common.sh + +# Test target_ids file +# ==================== + +file="$DBGFS/target_ids" +orig_content=$(cat "$file") + +test_write_succ "$file" "1 2 3 4" "$orig_content" "valid input" +test_write_succ "$file" "1 2 abc 4" "$orig_content" "still valid input" +test_content "$file" "$orig_content" "1 2" "non-integer was there" +test_write_succ "$file" "abc 2 3" "$orig_content" "the file allows wrong input" +test_content "$file" "$orig_content" "" "wrong input written" +test_write_succ "$file" "" "$orig_content" "empty input" +test_content "$file" "$orig_content" "" "empty input written" +echo "$orig_content" > "$file"
tools/testing/selftests/damon/Makefile renamed from tools/testing/selftests/damon/Makefile~selftests-damon-split-test-cases +3 -2
@@ -3,7 +3,8 @@ TEST_GEN_FILES += huge_count_read_write -TEST_FILES = _chk_dependency.sh -TEST_PROGS = debugfs_attrs.sh +TEST_FILES = _chk_dependency.sh _debugfs_common.sh +TEST_PROGS = debugfs_attrs.sh debugfs_schemes.sh debugfs_target_ids.sh +TEST_PROGS += debugfs_empty_targets.sh debugfs_huge_count_read_write.sh include ../lib.mk
_
Andrew Morton
maintainerPATCH 18/21 mm/slub: fix endianness bug for alloc/free_traces attributes
In reply to Andrew MortonFrom: Gerald Schaefer <[email protected]>
Subject: mm/slub: fix endianness bug for alloc/free_traces attributes
On big-endian s390, the alloc/free_traces attributes produce endless output, because of always 0 idx in slab_debugfs_show().
idx is de-referenced from *v, which points to a loff_t value, with
unsigned int idx = *(unsigned int *)v;
This will only give the upper 32 bits on big-endian, which remain 0.
Instead of only fixing this de-reference, during discussion it seemed more appropriate to change the seq_ops so that they use an explicit iterator in private loc_track struct.
This patch adds idx to loc_track, which will also fix the endianness bug.
---
mm/slub.c | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-)
mm/slub.c renamed from mm/slub.c~mm-slub-fix-endianness-bug-for-alloc-free_traces-attributes +9 -6
@@ -5081,6 +5081,7 @@ struct loc_track {unsigned long max;unsigned long count;struct location *loc; +loff_t idx; };static struct dentry *slab_debugfs_root;
@@ -6052,11 +6053,11 @@ __initcall(slab_sysfs_init);#if defined(CONFIG_SLUB_DEBUG ) && defined(CONFIG_DEBUG_FS )static int slab_debugfs_show (struct seq_file *seq,void *v) { - -struct location *l; -unsigned int idx = *(unsigned int *)v;struct loc_track *t = seq->private; +struct location *l; +unsigned long idx; + idx = (unsigned long ) t->idx;if (idx < t->count) { l = &t->loc[idx];
@@ -6105,16 +6106,18 @@ static void *slab_debugfs_next(struct se {struct loc_track *t = seq->private; - v = ppos; - ++*ppos; + t->idx = ++(*ppos);if (*ppos <= t->count) -return v; +return ppos;return NULL ; }static void *slab_debugfs_start (struct seq_file *seq,loff_t *ppos) { +struct loc_track *t = seq->private; + + t->idx = *ppos;return ppos; }
_
Andrew Morton
maintainerPATCH 19/21 mm/memcg: relocate mod_objcg_mlstate(), get_obj_stock() and put_obj_stock()
In reply to Andrew MortonFrom: Waiman Long <[email protected]>
Subject: mm/memcg: relocate mod_objcg_mlstate(), get_obj_stock() and put_obj_stock()
All the calls to mod_objcg_mlstate(), get_obj_stock() and put_obj_stock() are done by functions defined within the same "#ifdef CONFIG_MEMCG_KMEM" compilation block. When CONFIG_MEMCG_KMEM isn't defined, the following compilation warnings will be issued [1] and [2].
mm/memcontrol.c:785:20: warning: unused function 'mod_objcg_mlstate' mm/memcontrol.c:2113:33: warning: unused function 'get_obj_stock'
Fix these warning by moving those functions to under the same CONFIG_MEMCG_KMEM compilation block. There is no functional change.
[1] https://lore.kernel.org/lkml/[email protected]/
[2] https://lore.kernel.org/lkml/[email protected]/
---
mm/memcontrol.c | 106 +++++++++++++++++++++++----------------------- 1 file changed, 53 insertions(+), 53 deletions(-)
mm/memcontrol.c renamed from mm/memcontrol.c~mm-memcg-relocate-mod_objcg_mlstate-get_obj_stock-and-put_obj_stock +53 -53
@@ -776,24 +776,6 @@ void __mod_lruvec_kmem_state(void *p, enrcu_read_unlock (); } -/* -* mod_objcg_mlstate() may be called with irq enabled, so -* mod_memcg_lruvec_state() should be used. -*/ -static inline void mod_objcg_mlstate (struct obj_cgroup *objcg, -struct pglist_data *pgdat, -enum node_stat_item idx,int nr) -{ -struct mem_cgroup *memcg; -struct lruvec *lruvec; - -rcu_read_lock (); - memcg =obj_cgroup_memcg (objcg); - lruvec =mem_cgroup_lruvec (memcg, pgdat); -mod_memcg_lruvec_state (lruvec, idx, nr); -rcu_read_unlock (); -} -/** * __count_memcg_events - account VM events in a cgroup * @memcg: the memory cgroup
@@ -2137,41 +2119,6 @@ static bool obj_stock_flush_required(str }#endif -/* -* Most kmem_cache_alloc() calls are from user context. The irq disable/enable -* sequence used in this case to access content from object stock is slow. -* To optimize for user context access, there are now two object stocks for -* task context and interrupt context access respectively. -* -* The task context object stock can be accessed by disabling preemption only -* which is cheap in non-preempt kernel. The interrupt context object stock -* can only be accessed after disabling interrupt. User context code can -* access interrupt object stock, but not vice versa. -*/ -static inline struct obj_stock *get_obj_stock (unsigned long *pflags) -{ -struct memcg_stock_pcp *stock; - -if (likely (in_task ())) { - *pflags =0UL ; -preempt_disable (); - stock =this_cpu_ptr (&memcg_stock); -return &stock->task_obj; - } - -local_irq_save (*pflags); - stock =this_cpu_ptr (&memcg_stock); -return &stock->irq_obj; -} - -static inline void put_obj_stock (unsigned long flags) -{ -if (likely (in_task ())) -preempt_enable (); -else -local_irq_restore (flags); -} -/** * consume_stock: Try to consume stocked charge on this cpu. * @memcg: memcg to consume from.
@@ -2816,6 +2763,59 @@ retry:*/ #define OBJCGS_CLEAR_MASK (__GFP_DMA | __GFP_RECLAIMABLE | __GFP_ACCOUNT) +/* +* Most kmem_cache_alloc() calls are from user context. The irq disable/enable +* sequence used in this case to access content from object stock is slow. +* To optimize for user context access, there are now two object stocks for +* task context and interrupt context access respectively. +* +* The task context object stock can be accessed by disabling preemption only +* which is cheap in non-preempt kernel. The interrupt context object stock +* can only be accessed after disabling interrupt. User context code can +* access interrupt object stock, but not vice versa. +*/ +static inline struct obj_stock *get_obj_stock (unsigned long *pflags) +{ +struct memcg_stock_pcp *stock; + +if (likely (in_task ())) { + *pflags =0UL ; +preempt_disable (); + stock =this_cpu_ptr (&memcg_stock); +return &stock->task_obj; + } + +local_irq_save (*pflags); + stock =this_cpu_ptr (&memcg_stock); +return &stock->irq_obj; +} + +static inline void put_obj_stock (unsigned long flags) +{ +if (likely (in_task ())) +preempt_enable (); +else +local_irq_restore (flags); +} + +/* +* mod_objcg_mlstate() may be called with irq enabled, so +* mod_memcg_lruvec_state() should be used. +*/ +static inline void mod_objcg_mlstate (struct obj_cgroup *objcg, +struct pglist_data *pgdat, +enum node_stat_item idx,int nr) +{ +struct mem_cgroup *memcg; +struct lruvec *lruvec; + +rcu_read_lock (); + memcg =obj_cgroup_memcg (objcg); + lruvec =mem_cgroup_lruvec (memcg, pgdat); +mod_memcg_lruvec_state (lruvec, idx, nr); +rcu_read_unlock (); +} +int memcg_alloc_page_obj_cgroups (struct page *page,struct kmem_cache *s,gfp_t gfp,bool new_page) {
_
Andrew Morton
maintainerPATCH 20/21 hugetlbfs: fix issue of preallocation of gigantic pages can't work
In reply to Andrew MortonFrom: Zhenguo Yao <[email protected]>
Subject: hugetlbfs: fix issue of preallocation of gigantic pages can't work
Preallocation of gigantic pages can't work bacause of commit b5389086ad7b ("hugetlbfs: extend the definition of hugepages parameter to support node allocation"). When nid is NUMA_NO_NODE(-1), alloc_bootmem_huge_page will always return without doing allocation. Fix this by adding more check.
---
mm/hugetlb.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
mm/hugetlb.c renamed from mm/hugetlb.c~hugetlbfs-fix-issue-of-preallocation-of-gigantic-pages-cant-work +1 -1
@@ -2973,7 +2973,7 @@ int __alloc_bootmem_huge_page(struct hststruct huge_bootmem_page *m =NULL ;/* initialize for clang */ int nr_nodes, node; -if (nid >= nr_online_nodes) +if (nid !=NUMA_NO_NODE && nid >= nr_online_nodes)return 0 ;/* do node specific alloc */ if (nid !=NUMA_NO_NODE ) {
_
Andrew Morton
maintainerPATCH 21/21 mm: bdi: initialize bdi_min_ratio when bdi is unregistered
In reply to Andrew MortonFrom: Manjong Lee <[email protected]>
Subject: mm: bdi: initialize bdi_min_ratio when bdi is unregistered
Initialize min_ratio if it is set during bdi unregistration. This can prevent problems that may occur a when bdi is removed without resetting min_ratio.
For example.
1) insert external sdcard
2) set external sdcard's min_ratio 70
3) remove external sdcard without setting min_ratio 0
4) insert external sdcard
5) set external sdcard's min_ratio 70 << error occur(can't set)
Because when an sdcard is removed, the present bdi_min_ratio value will remain. Currently, the only way to reset bdi_min_ratio is to reboot.
---
mm/backing-dev.c | 7 +++++++ 1 file changed, 7 insertions(+)
mm/backing-dev.c renamed from mm/backing-dev.c~mm-bdi-initialize-bdi_min_ratio-when-bdi-unregister +7 -0
@@ -945,6 +945,13 @@ void bdi_unregister(struct backing_dev_iwb_shutdown (&bdi->wb);cgwb_bdi_unregister (bdi); +/* +* If this BDI's min ratio has been set, use bdi_set_min_ratio() to +* update the global bdi_min_ratio. +*/ +if (bdi->min_ratio) +bdi_set_min_ratio (bdi,0 ); +if (bdi->dev) {bdi_debug_unregister (bdi);device_unregister (bdi->dev);
_