[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YxrtODqHhdEkW2Lx@dhcp22.suse.cz>
Date: Fri, 9 Sep 2022 09:37:28 +0200
From: Michal Hocko <mhocko@...e.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Liu Shixin <liushixin2@...wei.com>,
Jonathan Corbet <corbet@....net>,
Johannes Weiner <hannes@...xchg.org>,
Roman Gushchin <roman.gushchin@...ux.dev>,
Shakeel Butt <shakeelb@...gle.com>,
Muchun Song <songmuchun@...edance.com>,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
cgroups@...r.kernel.org, linux-mm@...ck.org,
Kefeng Wang <wangkefeng.wang@...wei.com>
Subject: Re: [PATCH] mm/memcontrol: use kstrtobool for swapaccount param
parsing
On Thu 08-09-22 15:02:48, Andrew Morton wrote:
> On Thu, 8 Sep 2022 16:34:52 +0800 Liu Shixin <liushixin2@...wei.com> wrote:
>
> > --- a/mm/swap_cgroup.c
> > +++ b/mm/swap_cgroup.c
> > @@ -194,7 +194,7 @@ int swap_cgroup_swapon(int type, unsigned long max_pages)
> > return 0;
> > nomem:
> > pr_info("couldn't allocate enough memory for swap_cgroup\n");
> > - pr_info("swap_cgroup can be disabled by swapaccount=0 boot option\n");
> > + pr_info("swap_cgroup can be disabled by swapaccount=[oO][Ff]/N/n/0 boot option\n");
>
> I'm not sure this really needed changing. "=0" was OK and the message
> now looks rather silly.
Agreed. While swapaccount=0 is clear the extended form, even if correct,
might just confuse some admins.
--
Michal Hocko
SUSE Labs
Powered by blists - more mailing lists