The sysctl core is preparing to only expose instances of
struct ctl_table as "const".
This will also affect the ctl_table argument of sysctl handlers.
As the function prototype of all sysctl handlers throughout the tree
needs to stay consistent that change will be done in one commit.
pt/added the trailing comma for the ctl_table arrays. This was a comment
> > that we received "drivers/*" patch set.
> > * Link to v2:
> > https://lore.kernel.org/r/20230913-jag-sysctl_remove_empty_elem_arch-v2-0-d1bd13a29...@samsung.com
>
> Thanks! I replaced the v2 with th
drivers/*" patch set.
> * Link to v2:
> https://lore.kernel.org/r/20230913-jag-sysctl_remove_empty_elem_arch-v2-0-d1bd13a29...@samsung.com
Thanks! I replaced the v2 with this v3 on sysctl-next.
Luis
From: Joel Granados
What?
These commits remove the sentinel element (last empty element) from the
sysctl arrays of all the files under the "arch/" directory that use a
sysctl array for registration. The merging of the preparation patches
(in https://lore.kernel.org/all/zo5yx
nel.org/r/20230906-jag-sysctl_remove_empty_elem_arch-v1-0-3935d4854...@samsung.com
Thanks! I've merged this onto sysctl-next.
Luis
From: Joel Granados
What?
These commits remove the sentinel element (last empty element) from the
sysctl arrays of all the files under the "arch/" directory that use a
sysctl array for registration. The merging of the preparation patches
(in https://lore.kernel.org/all/zo5yx
dmin-guide/sysctl/kernel.rst | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/Documentation/admin-guide/sysctl/kernel.rst
b/Documentation/admin-guide/sysctl/kernel.rst
index 1d56a6b73a4e..7ca8df5451d4 100644
--- a/Documentation/admin-guide/sysctl/kernel.rst
+++ b/Doc
-Core: disable /sbin/hotplug by default")
Signed-off-by: Rasmus Villemoes
---
Documentation/admin-guide/sysctl/kernel.rst | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/Documentation/admin-guide/sysctl/kernel.rst
b/Documentation/admin-guide/sysctl/kernel.rst
index 1d
Committer: Peter Zijlstra
CommitterDate: Fri, 16 Apr 2021 17:06:34 +02:00
sched: Move SCHED_DEBUG sysctl to debugfs
Stop polluting sysctl with undocumented knobs that really are debug
only, move them all to /debug/sched/ along with the existing
/debug/sched_* files that already exist.
Signed-off
Committer: Peter Zijlstra
CommitterDate: Fri, 16 Apr 2021 17:06:33 +02:00
sched: Remove sched_schedstats sysctl out from under SCHED_DEBUG
CONFIG_SCHEDSTATS does not depend on SCHED_DEBUG, it is inconsistent
to have the sysctl depend on it.
Suggested-by: Mel Gorman
Signed-off-by: Peter Zijlstra
Committer: Peter Zijlstra
CommitterDate: Fri, 16 Apr 2021 17:06:35 +02:00
sched,debug: Convert sysctl sched_domains to debugfs
Stop polluting sysctl, move to debugfs for SCHED_DEBUG stuff.
Signed-off-by: Peter Zijlstra (Intel)
Reviewed-by: Dietmar Eggemann
Reviewed-by: Valentin Schneider
Tested
On Thu, Apr 15, 2021 at 01:34:27PM +0100, Valentin Schneider wrote:
> On 15/04/21 11:06, Peter Zijlstra wrote:
> > @@ -2388,8 +2384,6 @@ void partition_sched_domains_locked(int
> > doms_cur = doms_new;
> > dattr_cur = dattr_new;
> > ndoms_cur = ndoms_new;
> > -
> > -
On 15/04/21 11:06, Peter Zijlstra wrote:
> On Tue, Apr 13, 2021 at 03:55:15PM +0100, Valentin Schneider wrote:
>> On 12/04/21 12:14, Peter Zijlstra wrote:
>> > Stop polluting sysctl, move to debugfs for SCHED_DEBUG stuff.
>> >
>> > Signed-off-by: Peter Zijlstr
On 15/04/2021 11:06, Peter Zijlstra wrote:
> On Tue, Apr 13, 2021 at 03:55:15PM +0100, Valentin Schneider wrote:
>> On 12/04/21 12:14, Peter Zijlstra wrote:
>>> Stop polluting sysctl, move to debugfs for SCHED_DEBUG stuff.
>>>
>>> Signed-off-by: Peter Zijlst
On Tue, Apr 13, 2021 at 03:55:15PM +0100, Valentin Schneider wrote:
> On 12/04/21 12:14, Peter Zijlstra wrote:
> > Stop polluting sysctl, move to debugfs for SCHED_DEBUG stuff.
> >
> > Signed-off-by: Peter Zijlstra (Intel)
> > Reviewed-by: Dietmar Eggemann
>
>
On 12/04/21 12:14, Peter Zijlstra wrote:
> Stop polluting sysctl, move to debugfs for SCHED_DEBUG stuff.
>
> Signed-off-by: Peter Zijlstra (Intel)
> Reviewed-by: Dietmar Eggemann
On my Juno (2+4 big.LITTLE), sys/kernel/debug/sched/domains/ is now empty.
I think th
Stop polluting sysctl, move to debugfs for SCHED_DEBUG stuff.
Signed-off-by: Peter Zijlstra (Intel)
Reviewed-by: Dietmar Eggemann
---
kernel/sched/debug.c| 255 +++-
kernel/sched/sched.h|2
kernel/sched/topology.c |1
3 files
Stop polluting sysctl with undocumented knobs that really are debug
only, move them all to /debug/sched/ along with the existing
/debug/sched_* files that already exist.
Signed-off-by: Peter Zijlstra (Intel)
Reviewed-by: Greg Kroah-Hartman
---
include/linux/sched/sysctl.h |8 +--
kernel
CONFIG_SCHEDSTATS does not depend on SCHED_DEBUG, it is inconsistent
to have the sysctl depend on it.
Suggested-by: Mel Gorman
Signed-off-by: Peter Zijlstra (Intel)
---
kernel/sysctl.c | 22 +++---
1 file changed, 11 insertions(+), 11 deletions(-)
--- a/kernel/sysctl.c
+++ b
On Tue, Mar 2, 2021 at 8:47 AM Kees Cook wrote:
>
> On Sun, Feb 28, 2021 at 04:44:22PM +0900, Masahiro Yamada wrote:
> > (CC: Andrew Morton)
> >
> > A friendly reminder.
> >
> >
> > This is just a minor clean-up.
> >
> > If nobody picks it up,
> > I hope perhaps Andrew Morton will do.
> >
> >
On Wed, Apr 07, 2021 at 11:46:32AM +0100, Valentin Schneider wrote:
> > - __cpumask_clear_cpu(i, sd_sysctl_cpus);
>
> That seems to be the only place we cleared a CPU in that cpumask, and I
> don't see its replacement
Yeah, oops :-) Lemme go fix that. Thanks!
On 26/03/21 11:33, Peter Zijlstra wrote:
> Stop polluting sysctl, move to debugfs for SCHED_DEBUG stuff.
>
> Signed-off-by: Peter Zijlstra (Intel)
> ---
> kernel/sched/debug.c| 255
> ++--
> kernel/sched/sched.h|
submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url:
https://github.com/0day-ci/linux/commits/Alexey-Avramov/mm-vmscan-add-sysctl-knobs-for-protecting-the-specified/20210406-061034
base: https://git.kernel.org/pub/scm/linux/kernel/git
patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url:
https://github.com/0day-ci/linux/commits/Alexey-Avramov/mm-vmscan-add-sysctl-knobs-for-protecting-the-specified/20210406-061034
base: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds
Update the toptier_scale_factor via sysctl. This variable determines
when kswapd wakes up to recalaim toptier memory from those mem cgroups
exceeding their toptier memory limit.
Signed-off-by: Tim Chen
---
include/linux/mm.h | 4
include/linux/mmzone.h | 2 ++
kernel/sysctl.c
On 26/03/2021 11:33, Peter Zijlstra wrote:
> Stop polluting sysctl, move to debugfs for SCHED_DEBUG stuff.
>
> Signed-off-by: Peter Zijlstra (Intel)
> ---
> kernel/sched/debug.c| 255
> ++--
> kernel/sched/sched.h|
Stop polluting sysctl, move to debugfs for SCHED_DEBUG stuff.
Signed-off-by: Peter Zijlstra (Intel)
---
kernel/sched/debug.c| 255 ++--
kernel/sched/sched.h|2
kernel/sched/topology.c |1
3 files changed, 59 insertions(+), 199
CONFIG_SCHEDSTATS does not depend on SCHED_DEBUG, it is inconsistent
to have the sysctl depend on it.
Suggested-by: Mel Gorman
Signed-off-by: Peter Zijlstra (Intel)
---
kernel/sysctl.c | 22 +++---
1 file changed, 11 insertions(+), 11 deletions(-)
--- a/kernel/sysctl.c
+++ b
Add binding documentation for the GPIO sysctl found in BCM6318 SoCs.
Signed-off-by: Álvaro Fernández Rojas
Reviewed-by: Rob Herring
---
v9: no changes
v8: add changes suggested by Rob Herring
v7: add changes suggested by Rob Herring
.../mfd/brcm,bcm6318-gpio-sysctl.yaml | 177
Add binding documentation for the GPIO sysctl found in BCM6368 SoCs.
Signed-off-by: Álvaro Fernández Rojas
Reviewed-by: Rob Herring
---
v9: no changes
v8: add changes suggested by Rob Herring
v7: add changes suggested by Rob Herring
.../mfd/brcm,bcm6368-gpio-sysctl.yaml | 246
Add binding documentation for the GPIO sysctl found in BCM6362 SoCs.
Signed-off-by: Álvaro Fernández Rojas
Reviewed-by: Rob Herring
---
v9: no changes
v8: add changes suggested by Rob Herring
v7: add changes suggested by Rob Herring
.../mfd/brcm,bcm6362-gpio-sysctl.yaml | 236
Add binding documentation for the GPIO sysctl found in BCM63268 SoCs.
Signed-off-by: Álvaro Fernández Rojas
Reviewed-by: Rob Herring
---
v9: no changes
v8: add changes suggested by Rob Herring
v7: add changes suggested by Rob Herring
.../mfd/brcm,bcm63268-gpio-sysctl.yaml| 194
Add binding documentation for the GPIO sysctl found in BCM6328 SoCs.
Signed-off-by: Álvaro Fernández Rojas
Reviewed-by: Rob Herring
---
v9: no changes
v8: add changes suggested by Rob Herring
v7: add changes suggested by Rob Herring
.../mfd/brcm,bcm6328-gpio-sysctl.yaml | 162
Add binding documentation for the GPIO sysctl found in BCM6358 SoCs.
Signed-off-by: Álvaro Fernández Rojas
Reviewed-by: Rob Herring
---
v9: no changes
v8: add changes suggested by Rob Herring
v7: add changes suggested by Rob Herring
.../mfd/brcm,bcm6358-gpio-sysctl.yaml | 130
On Wed, 17 Mar 2021 15:38:02 +0100, Álvaro Fernández Rojas wrote:
> Add binding documentation for the GPIO sysctl found in BCM6318 SoCs.
>
> Signed-off-by: Álvaro Fernández Rojas
> ---
> v8: add changes suggested by Rob Herring
> v7: add changes suggested by Rob Herring
On Wed, 17 Mar 2021 15:37:59 +0100, Álvaro Fernández Rojas wrote:
> Add binding documentation for the GPIO sysctl found in BCM63268 SoCs.
>
> Signed-off-by: Álvaro Fernández Rojas
> ---
> v8: add changes suggested by Rob Herring
> v7: add changes suggested by Rob Herring
On Wed, 17 Mar 2021 15:37:56 +0100, Álvaro Fernández Rojas wrote:
> Add binding documentation for the GPIO sysctl found in BCM6368 SoCs.
>
> Signed-off-by: Álvaro Fernández Rojas
> ---
> v8: add changes suggested by Rob Herring
> v7: add changes suggested by Rob Herring
On Wed, 17 Mar 2021 15:37:53 +0100, Álvaro Fernández Rojas wrote:
> Add binding documentation for the GPIO sysctl found in BCM6362 SoCs.
>
> Signed-off-by: Álvaro Fernández Rojas
> ---
> v8: add changes suggested by Rob Herring
> v7: add changes suggested by Rob Herring
On Wed, 17 Mar 2021 15:37:50 +0100, Álvaro Fernández Rojas wrote:
> Add binding documentation for the GPIO sysctl found in BCM6358 SoCs.
>
> Signed-off-by: Álvaro Fernández Rojas
> ---
> v8: add changes suggested by Rob Herring
> v7: add changes suggested by Rob Herring
On Wed, Mar 17, 2021 at 03:37:47PM +0100, Álvaro Fernández Rojas wrote:
> Add binding documentation for the GPIO sysctl found in BCM6328 SoCs.
>
> Signed-off-by: Álvaro Fernández Rojas
> ---
> v8: add changes suggested by Rob Herring
> v7: add changes suggested by Rob H
Add binding documentation for the GPIO sysctl found in BCM6318 SoCs.
Signed-off-by: Álvaro Fernández Rojas
---
v8: add changes suggested by Rob Herring
v7: add changes suggested by Rob Herring
.../mfd/brcm,bcm6318-gpio-sysctl.yaml | 177 ++
1 file changed, 177
Add binding documentation for the GPIO sysctl found in BCM63268 SoCs.
Signed-off-by: Álvaro Fernández Rojas
---
v8: add changes suggested by Rob Herring
v7: add changes suggested by Rob Herring
.../mfd/brcm,bcm63268-gpio-sysctl.yaml| 194 ++
1 file changed, 194
Add binding documentation for the GPIO sysctl found in BCM6368 SoCs.
Signed-off-by: Álvaro Fernández Rojas
---
v8: add changes suggested by Rob Herring
v7: add changes suggested by Rob Herring
.../mfd/brcm,bcm6368-gpio-sysctl.yaml | 246 ++
1 file changed, 246
Add binding documentation for the GPIO sysctl found in BCM6362 SoCs.
Signed-off-by: Álvaro Fernández Rojas
---
v8: add changes suggested by Rob Herring
v7: add changes suggested by Rob Herring
.../mfd/brcm,bcm6362-gpio-sysctl.yaml | 236 ++
1 file changed, 236
Add binding documentation for the GPIO sysctl found in BCM6358 SoCs.
Signed-off-by: Álvaro Fernández Rojas
---
v8: add changes suggested by Rob Herring
v7: add changes suggested by Rob Herring
.../mfd/brcm,bcm6358-gpio-sysctl.yaml | 130 ++
1 file changed, 130
Add binding documentation for the GPIO sysctl found in BCM6328 SoCs.
Signed-off-by: Álvaro Fernández Rojas
---
v8: add changes suggested by Rob Herring
v7: add changes suggested by Rob Herring
.../mfd/brcm,bcm6328-gpio-sysctl.yaml | 162 ++
1 file changed, 162
Hi Rob,
> El 16 mar 2021, a las 22:20, Rob Herring escribió:
>
> On Mon, Mar 15, 2021 at 5:42 AM Álvaro Fernández Rojas
> wrote:
>>
>> Add binding documentation for the GPIO sysctl found in BCM6318 SoCs.
>>
>> Signed-off-by: Álvaro Fernández Rojas
>&g
On Mon, Mar 15, 2021 at 5:42 AM Álvaro Fernández Rojas
wrote:
>
> Add binding documentation for the GPIO sysctl found in BCM6318 SoCs.
>
> Signed-off-by: Álvaro Fernández Rojas
> ---
> v7: add changes suggested by Rob Herring
>
> .../mfd/brcm,bcm6318-gpio-s
On Mon, Mar 15, 2021 at 04:19:54AM -0700, zhouchuangao wrote:
> The function name should be modified to register_sysctl_paths instead
> of register_sysctl_table_path.
>
> Signed-off-by: zhouchuangao
Acked-by: Luis Chamberlain
Luis
Add binding documentation for the GPIO sysctl found in BCM6318 SoCs.
Signed-off-by: Álvaro Fernández Rojas
---
v7: add changes suggested by Rob Herring
.../mfd/brcm,bcm6318-gpio-sysctl.yaml | 179 ++
1 file changed, 179 insertions(+)
create mode 100644
Documentation
Add binding documentation for the GPIO sysctl found in BCM63268 SoCs.
Signed-off-by: Álvaro Fernández Rojas
---
v7: add changes suggested by Rob Herring
.../mfd/brcm,bcm63268-gpio-sysctl.yaml| 196 ++
1 file changed, 196 insertions(+)
create mode 100644
Documentation
Add binding documentation for the GPIO sysctl found in BCM6368 SoCs.
Signed-off-by: Álvaro Fernández Rojas
---
v7: add changes suggested by Rob Herring
.../mfd/brcm,bcm6368-gpio-sysctl.yaml | 248 ++
1 file changed, 248 insertions(+)
create mode 100644
Documentation
Add binding documentation for the GPIO sysctl found in BCM6362 SoCs.
Signed-off-by: Álvaro Fernández Rojas
---
v7: add changes suggested by Rob Herring
.../mfd/brcm,bcm6362-gpio-sysctl.yaml | 238 ++
1 file changed, 238 insertions(+)
create mode 100644
Documentation
Add binding documentation for the GPIO sysctl found in BCM6358 SoCs.
Signed-off-by: Álvaro Fernández Rojas
---
v7: add changes suggested by Rob Herring
.../mfd/brcm,bcm6358-gpio-sysctl.yaml | 132 ++
1 file changed, 132 insertions(+)
create mode 100644
Documentation
Add binding documentation for the GPIO sysctl found in BCM6328 SoCs.
Signed-off-by: Álvaro Fernández Rojas
---
v7: add changes suggested by Rob Herring
.../mfd/brcm,bcm6328-gpio-sysctl.yaml | 164 ++
1 file changed, 164 insertions(+)
create mode 100644
Documentation
100644
--- a/fs/proc/proc_sysctl.c
+++ b/fs/proc/proc_sysctl.c
@@ -1562,7 +1562,7 @@ struct ctl_table_header *__register_sysctl_paths(
}
/**
- * register_sysctl_table_path - register a sysctl table hierarchy
+ * register_sysctl_paths - register a sysctl table hierarchy
* @path: The path
On Sun, Feb 28, 2021 at 04:44:22PM +0900, Masahiro Yamada wrote:
> (CC: Andrew Morton)
>
> A friendly reminder.
>
>
> This is just a minor clean-up.
>
> If nobody picks it up,
> I hope perhaps Andrew Morton will do.
>
> This patch:
> https://lore.kernel.org/patchwork/patch/1360092/
>
>
>
>
(CC: Andrew Morton)
A friendly reminder.
This is just a minor clean-up.
If nobody picks it up,
I hope perhaps Andrew Morton will do.
This patch:
https://lore.kernel.org/patchwork/patch/1360092/
On Mon, Jan 4, 2021 at 5:33 PM Masahiro Yamada wrote:
>
> Make it slightly readable by using
On Wed, Feb 24, 2021 at 05:02:09PM -0800, Ivan Babrou wrote:
> Hello,
>
> We started seeing allocation failures on procfs reads after
> commit 4bd6a7353ee1 "sysctl: Convert to iter interfaces".
https://lore.kernel.org/linux-fsdevel/6345270a2c1160b89dd5e6715461f3881768
Hello,
We started seeing allocation failures on procfs reads after
commit 4bd6a7353ee1 "sysctl: Convert to iter interfaces".
I haven't done a full bisect, but the decoded stacks point
squarely at the following piece of code which was introduced:
kbuf = kzalloc(count + 1,
From: Christian Brauner
commit 7f2923c4f73f21cfd714d12a2d48de8c21f11cfe upstream.
proc_get_long() is a funny function. It uses simple_strtoul() and for a
good reason. proc_get_long() wants to always succeed the parse and
return the maybe incorrect value and the trailing characters to check
From: Eyal Birger
[ Upstream commit 9f8550e4bd9d78a8436c2061ad2530215f875376 ]
The disable_xfrm flag signals that xfrm should not be performed during
routing towards a device before reaching device xmit.
For xfrm interfaces this is usually desired as they perform the outbound
policy lookup as
From: Eyal Birger
[ Upstream commit 9f8550e4bd9d78a8436c2061ad2530215f875376 ]
The disable_xfrm flag signals that xfrm should not be performed during
routing towards a device before reaching device xmit.
For xfrm interfaces this is usually desired as they perform the outbound
policy lookup as
From: Eyal Birger
[ Upstream commit 9f8550e4bd9d78a8436c2061ad2530215f875376 ]
The disable_xfrm flag signals that xfrm should not be performed during
routing towards a device before reaching device xmit.
For xfrm interfaces this is usually desired as they perform the outbound
policy lookup as
On Wed, 20 Jan 2021 13:26:47 +
Eric Curtin wrote:
> max_user_watches for epoll should say 1/25, rather than 1/32
>
> Signed-off-by: Eric Curtin
> ---
> Documentation/admin-guide/sysctl/fs.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --g
d-off-by: Masahiro Yamada
>
> [...]
Here is the summary with links:
- net: sysctl: remove redundant #ifdef CONFIG_NET
https://git.kernel.org/netdev/net-next/c/69783429cd13
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
CONFIG_NET is a bool option, and this file is compiled only when
CONFIG_NET=y.
Remove #ifdef CONFIG_NET, which we know it is always met.
Signed-off-by: Masahiro Yamada
---
net/core/sysctl_net_core.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/net/core/sysctl_net_core.c
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Thu, 21 Jan 2021 16:02:44 +0100 you wrote:
> This patch adds documentation for sysctl conf/all/disable_ipv6 and
> conf/default/disable_ipv6 settings which is currently missing.
>
> Signed-off-by
This patch adds documentation for sysctl conf/all/disable_ipv6 and
conf/default/disable_ipv6 settings which is currently missing.
Signed-off-by: Pali Rohár
---
Documentation/networking/ip-sysctl.rst | 12
1 file changed, 12 insertions(+)
diff --git a/Documentation/networking/ip
max_user_watches for epoll should say 1/25, rather than 1/32
Signed-off-by: Eric Curtin
---
Documentation/admin-guide/sysctl/fs.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/admin-guide/sysctl/fs.rst
b/Documentation/admin-guide/sysctl/fs.rst
index
From: Menglong Dong
For now, most sysctl in 'net/core' are globally unified, such as
sysctl_wmem_default, sysctl_rmem_default, sysctl_wmem_default,
sysctl_rmem_default, etc.
It's not convenient in some case. For example, when we use docker
and try to control the default udp socket receive
On Thu, 07 Jan 2021 09:13:40 + Alexander Lobakin wrote:
> From: Jakub Kicinski
> Date: Wed, 6 Jan 2021 16:30:56 -0800
>
> > On Wed, 06 Jan 2021 20:40:28 + Alexander Lobakin wrote:
> >> 'net_header' is not used outside of this function, so can be moved
> >> from BSS onto the stack.
> >>
From: Jakub Kicinski
Date: Wed, 6 Jan 2021 16:30:56 -0800
> On Wed, 06 Jan 2021 20:40:28 + Alexander Lobakin wrote:
>> 'net_header' is not used outside of this function, so can be moved
>> from BSS onto the stack.
>> Declarations of one-element arrays are discouraged, and there's no
>> need
On Wed, 06 Jan 2021 20:40:28 + Alexander Lobakin wrote:
> 'net_header' is not used outside of this function, so can be moved
> from BSS onto the stack.
> Declarations of one-element arrays are discouraged, and there's no
> need to store 'empty' in BSS. Simply allocate it from heap at init.
On Mon, Jan 04, 2021 at 05:32:21PM +0900, Masahiro Yamada wrote:
> Make it slightly readable by using min().
>
> Signed-off-by: Masahiro Yamada
Acked-by: Kees Cook
--
Kees Cook
= sysctl_net_exit,
};
-static struct ctl_table_header *net_header;
__init int net_sysctl_init(void)
{
- static struct ctl_table empty[1];
+ struct ctl_table_header *net_header;
+ struct ctl_table *empty;
int ret = -ENOMEM;
+
/* Avoid limitations in the sysctl
Make it slightly readable by using min().
Signed-off-by: Masahiro Yamada
---
fs/proc/proc_sysctl.c | 7 +--
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/fs/proc/proc_sysctl.c b/fs/proc/proc_sysctl.c
index 317899222d7f..86341c0f0c40 100644
--- a/fs/proc/proc_sysctl.c
+++
5535-5) in include/linux/mm.h
>
> #define MAPCOUNT_ELF_CORE_MARGIN(5)
> #define DEFAULT_MAX_MAP_COUNT (USHRT_MAX - MAPCOUNT_ELF_CORE_MARGIN)
>
> Signed-off-by: Fengfei Xi
> ---
> Documentation/admin-guide/sysctl/vm.rst | 2 +-
> 1 file changed, 1 i
)
#define DEFAULT_MAX_MAP_COUNT (USHRT_MAX - MAPCOUNT_ELF_CORE_MARGIN)
Signed-off-by: Fengfei Xi
---
Documentation/admin-guide/sysctl/vm.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/admin-guide/sysctl/vm.rst
b/Documentation/admin-guide/sysctl/vm.rst
index
cked against current kernels.
>
> Signed-off-by: Stephen Kitt
> ---
> Documentation/admin-guide/sysctl/kernel.rst | 14 +++---
> 1 file changed, 7 insertions(+), 7 deletions(-)
Applied, thanks.
jon
/admin-guide/sysctl/kernel.rst | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/Documentation/admin-guide/sysctl/kernel.rst
b/Documentation/admin-guide/sysctl/kernel.rst
index d4b32cc32bb7..7d53146798c0 100644
--- a/Documentation/admin-guide/sysctl/kernel.rst
+++ b
loading.
This may be seen as a way for a trusted task (e.g. interpreter) to check
the trustworthiness of files (e.g. scripts) before extending its control
flow graph with new ones originating from these files.
The security policy is consistently managed by the kernel through the
new sysctl
sys/sysctl.conf.
>
> The main reason this change is desirable as in the short term is that
> the Android userland will behave as with the sysctl set to zero. So
> without this commit, any Linux binary using userfaultfd to manage its
> memory would behave differently if run within the A
as with the sysctl set to zero. So
without this commit, any Linux binary using userfaultfd to manage its
memory would behave differently if run within the Android userland.
For more details, refer to Andrea's reply [1].
[1] https://lore.kernel.org/lkml/20200904033438.gi9...@redhat.com/
Signed-off-by: Lokesh Gidra
g-analyzer-deadcode.DeadStores]
> > first = 0;
> > ^
> >
> > Commit 9f977fb7ae9d ("sysctl: add proc_do_large_bitmap") introduced
> > proc_do_large_bitmap(), where the variable first is only effectively used
> > when write
^
>
> Commit 9f977fb7ae9d ("sysctl: add proc_do_large_bitmap") introduced
> proc_do_large_bitmap(), where the variable first is only effectively used
> when write is false; when write is true, the variable first is only used in
> a dead assignment.
>
> So, simply
first = 0;
> ^
>
> Commit 9f977fb7ae9d ("sysctl: add proc_do_large_bitmap") introduced
> proc_do_large_bitmap(), where the variable first is only effectively used
> when write is false; when write is true, the variable first is only used in
> a dead assignment.
On Mon, Nov 09, 2020 at 05:06:18PM +0100, Michal Hocko wrote:
> On Mon 09-11-20 07:39:33, Minchan Kim wrote:
> > On Mon, Nov 09, 2020 at 08:37:06AM +0100, Michal Hocko wrote:
> > > On Fri 06-11-20 12:32:38, Minchan Kim wrote:
> > > > It's hard to have some tests to be supposed to work under heavy
On Mon 09-11-20 07:39:33, Minchan Kim wrote:
> On Mon, Nov 09, 2020 at 08:37:06AM +0100, Michal Hocko wrote:
> > On Fri 06-11-20 12:32:38, Minchan Kim wrote:
> > > It's hard to have some tests to be supposed to work under heavy
> > > memory pressure(e.g., injecting some memory hogger) because
> >
On Mon, Nov 09, 2020 at 08:37:06AM +0100, Michal Hocko wrote:
> On Fri 06-11-20 12:32:38, Minchan Kim wrote:
> > It's hard to have some tests to be supposed to work under heavy
> > memory pressure(e.g., injecting some memory hogger) because
> > out-of-memory killer easily kicks out one of
On Fri 06-11-20 12:32:38, Minchan Kim wrote:
> It's hard to have some tests to be supposed to work under heavy
> memory pressure(e.g., injecting some memory hogger) because
> out-of-memory killer easily kicks out one of processes so system
> is broken or system loses the memory pressure state
make clang-analyzer caught my attention with:
kernel/sysctl.c:1511:4: warning: Value stored to 'first' is never read \
[clang-analyzer-deadcode.DeadStores]
first = 0;
^
Commit 9f977fb7ae9d ("sysctl: add proc_do_large_bitmap")
On Fri, Nov 06, 2020 at 12:46:47PM -0800, Randy Dunlap wrote:
> Hi,
>
> Fix a few typos:
>
> On 11/6/20 12:32 PM, Minchan Kim wrote:
> > ---
> > Documentation/admin-guide/sysctl/vm.rst | 14 ++
> > include/linux/mm.h
Hi,
Fix a few typos:
On 11/6/20 12:32 PM, Minchan Kim wrote:
> ---
> Documentation/admin-guide/sysctl/vm.rst | 14 ++
> include/linux/mm.h | 2 ++
> include/linux/oom.h | 1 +
> kernel/sysctl.c | 9
we could mark existing process's oom_adj to -1000,
it couldn't cover upcoming processes to be forked for the job.
This knob is handy to keep system memory pressure.
Signed-off-by: Minchan Kim
---
Documentation/admin-guide/sysctl/vm.rst | 14 ++
include/linux/mm.h
From: Artur Molchanov
commit c09f56b8f68d4d536bff518227aea323b835b2ce upstream.
Fix returning value for sysctl sunrpc.transports.
Return error code from sysctl proc_handler function proc_do_xprt instead of
number of the written bytes.
Otherwise sysctl returns random garbage for this key
as with the sysctl set to zero. So
without this commit, any Linux binary using userfaultfd to manage its
memory would behave differently if run within the Android userland.
For more details, refer to Andrea's reply [1].
[1] https://lore.kernel.org/lkml/20200904033438.gi9...@redhat.com/
Signed-off-by: Lokesh Gidra
This is a previous step to add the detection feature.
A fork brute force attack will be detected when an application crashes
quickly. Since, the application crash period is the time between the
execve system call and the first fault or the time between two
consecutives faults add a new sysctl
o the below would be a
> summary that could be added to the commit header:
>
> ==
>
> The main reason this change is desirable as in the short term is that
> the Android userland will behave as with the sysctl set to zero. So
> without this commit, any Linux binary using userfaultfd to manage
ernel default with the post-boot Android default.
The email in the link above was pretty long, so the below would be a
summary that could be added to the commit header:
==
The main reason this change is desirable as in the short term is that
the Android userland will behave as with the sysctl set to zero
1 - 100 of 5209 matches
Mail list logo
