mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: wenyang.linux@foxmail.com
To: Luis Chamberlain <mcgrof@kernel.org>,
	Kees Cook <keescook@chromium.org>,
	Joel Granados <j.granados@samsung.com>,
	Christian Brauner <brauner@kernel.org>,
	davem@davemloft.net, David Ahern <dsahern@kernel.org>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: Wen Yang <wenyang.linux@foxmail.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/8] introduce sysctl SYSCTL_U8_MAX and SYSCTL_LONG_S32_MAX
Date: Sun, 25 Feb 2024 12:05:30 +0800	[thread overview]
Message-ID: <tencent_275FF7F351D515B570D0F82447BA30F3AA06@qq.com> (raw)

From: Wen Yang <wenyang.linux@foxmail.com>

The boundary check of multiple modules uses these static variables (such as
two_five_five, n_65535, ue_int_max, etc), and they are also not changed.
Therefore, add them to the shared sysctl_vals and sysctl_long_vals to avoid
duplication. This also reduce the size a bit 

Wen Yang (8):
  sysctl: introduce sysctl SYSCTL_U8_MAX and SYSCTL_LONG_S32_MAX
  rxrpc: delete these duplicate static variables n_65535 and four
  net: ipv6: delete these duplicate static variables two_five_five and
    minus_one
  svcrdma: delete the duplicate static variables zero
  sysctl: delete these duplicate static variables i_zero and
    i_one_hundred
  epoll: delete these duplicate static variables long_zero and long_max
  fs: inotify: delete these duplicate static variables it_zero and
    it_int_max
  ucounts: delete these duplicate static variables ue_zero and
    ue_int_max

 fs/eventpoll.c                   |  7 ++-----
 fs/notify/inotify/inotify_user.c | 11 ++++-------
 include/linux/sysctl.h           | 15 +++++++++------
 kernel/sysctl.c                  |  4 ++--
 kernel/ucount.c                  |  7 ++-----
 lib/test_sysctl.c                |  6 ++----
 net/ipv6/addrconf.c              | 12 +++++-------
 net/rxrpc/sysctl.c               | 16 +++++++---------
 net/sunrpc/xprtrdma/svc_rdma.c   | 21 ++++++++++-----------
 9 files changed, 43 insertions(+), 56 deletions(-)

Cc: Luis Chamberlain <mcgrof@kernel.org>
Cc: Kees Cook <keescook@chromium.org>
Cc: Joel Granados <j.granados@samsung.com>
Cc: Christian Brauner <brauner@kernel.org>
Cc: "David S. Miller" <davem@davemloft.net>
Cc: David Ahern <dsahern@kernel.org>
Cc: Eric Dumazet <edumazet@google.com>
Cc: Jakub Kicinski <kuba@kernel.org>
Cc: Paolo Abeni <pabeni@redhat.com>
Cc: netdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org

-- 
2.25.1


             reply	other threads:[~2024-02-25  4:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20240225040621eucas1p281f4ae53ecc8c0e1979fdc0c6b09643f@eucas1p2.samsung.com>
2024-02-25  4:05 ` wenyang.linux [this message]
2024-02-25 20:15   ` Joel Granados
2024-02-26 15:28   ` Jakub Kicinski
2024-02-28 12:30     ` Wen Yang

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=tencent_275FF7F351D515B570D0F82447BA30F3AA06@qq.com \
    --to=wenyang.linux@foxmail.com \
    --cc=brauner@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=j.granados@samsung.com \
    --cc=keescook@chromium.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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

all inboxes | Powered by JetHome®