From: Michal Hocko <mhocko@kernel.org> To: SF Markus Elfring <elfring@users.sourceforge.net> Cc: iommu@lists.linux-foundation.org, kasan-dev@googlegroups.com, Alexander Potapenko <glider@google.com>, Andrew Morton <akpm@linux-foundation.org>, Andrey Ryabinin <aryabinin@virtuozzo.com>, Andy Shevchenko <andriy.shevchenko@linux.intel.com>, Christoph Hellwig <hch@lst.de>, Daniel Mentz <danielmentz@google.com>, Dmitry Vyukov <dvyukov@google.com>, Geert Uytterhoeven <geert@linux-m68k.org>, Lars Ellenberg <lars.ellenberg@linbit.com>, "Luis R. Rodriguez" <mcgrof@kernel.org>, Marek Szyprowski <m.szyprowski@samsung.com>, Mathieu Desnoyers <mathieu.desnoyers@efficios.com>, Philipp Reisner <philipp.reisner@linbit.com>, Robin Murphy <robin.murphy@arm.com>, Will Deacon <will.deacon@arm.com>, LKML <linux-kernel@vger.kernel.org>, kernel-janitors@vger.kernel.org Subject: Re: [PATCH 1/2] lib/test: Delete five error messages for a failed memory allocation Date: Mon, 9 Oct 2017 08:24:39 +0200 [thread overview] Message-ID: <20171009062439.oxocubhhhnd7t23c@dhcp22.suse.cz> (raw) In-Reply-To: <410a4c5a-4ee0-6fcc-969c-103d8e496b78@users.sourceforge.net> On Sat 07-10-17 19:48:37, SF Markus Elfring wrote: > From: Markus Elfring <elfring@users.sourceforge.net> > Date: Sat, 7 Oct 2017 17:34:23 +0200 > > Omit extra messages for a memory allocation failure in these functions. > > This issue was detected by using the Coccinelle software. Yes this makes sense. None of those really explain what the allocation failure effect is. The allocation path already tells us about the failure enough. > Signed-off-by: Markus Elfring <elfring@users.sourceforge.net> Acked-by: Michal Hocko <mhocko@suse.com> > --- > lib/test_kasan.c | 5 ++--- > lib/test_kmod.c | 8 ++------ > lib/test_list_sort.c | 9 +++------ > 3 files changed, 7 insertions(+), 15 deletions(-) > > diff --git a/lib/test_kasan.c b/lib/test_kasan.c > index a25c9763fce1..ef1a3ac1397e 100644 > --- a/lib/test_kasan.c > +++ b/lib/test_kasan.c > @@ -353,10 +353,9 @@ static noinline void __init memcg_accounted_kmem_cache(void) > */ > for (i = 0; i < 5; i++) { > p = kmem_cache_alloc(cache, GFP_KERNEL); > - if (!p) { > - pr_err("Allocation failed\n"); > + if (!p) > goto free_cache; > - } > + > kmem_cache_free(cache, p); > msleep(100); > } > diff --git a/lib/test_kmod.c b/lib/test_kmod.c > index fba78d25e825..337f408b4de6 100644 > --- a/lib/test_kmod.c > +++ b/lib/test_kmod.c > @@ -783,10 +783,8 @@ static int kmod_config_sync_info(struct kmod_test_device *test_dev) > free_test_dev_info(test_dev); > test_dev->info = vzalloc(config->num_threads * > sizeof(struct kmod_test_device_info)); > - if (!test_dev->info) { > - dev_err(test_dev->dev, "Cannot alloc test_dev info\n"); > + if (!test_dev->info) > return -ENOMEM; > - } > > return 0; > } > @@ -1089,10 +1087,8 @@ static struct kmod_test_device *alloc_test_dev_kmod(int idx) > struct miscdevice *misc_dev; > > test_dev = vzalloc(sizeof(struct kmod_test_device)); > - if (!test_dev) { > - pr_err("Cannot alloc test_dev\n"); > + if (!test_dev) > goto err_out; > - } > > mutex_init(&test_dev->config_mutex); > mutex_init(&test_dev->trigger_mutex); > diff --git a/lib/test_list_sort.c b/lib/test_list_sort.c > index 28e817387b04..5474f3f3e41d 100644 > --- a/lib/test_list_sort.c > +++ b/lib/test_list_sort.c > @@ -76,17 +76,14 @@ static int __init list_sort_test(void) > pr_debug("start testing list_sort()\n"); > > elts = kcalloc(TEST_LIST_LEN, sizeof(*elts), GFP_KERNEL); > - if (!elts) { > - pr_err("error: cannot allocate memory\n"); > + if (!elts) > return err; > - } > > for (i = 0; i < TEST_LIST_LEN; i++) { > el = kmalloc(sizeof(*el), GFP_KERNEL); > - if (!el) { > - pr_err("error: cannot allocate memory\n"); > + if (!el) > goto exit; > - } > + > /* force some equivalencies */ > el->value = prandom_u32() % (TEST_LIST_LEN / 3); > el->serial = i; > -- > 2.14.2 -- Michal Hocko SUSE Labs
WARNING: multiple messages have this Message-ID (diff)
From: Michal Hocko <mhocko@kernel.org> To: SF Markus Elfring <elfring@users.sourceforge.net> Cc: iommu@lists.linux-foundation.org, kasan-dev@googlegroups.com, Alexander Potapenko <glider@google.com>, Andrew Morton <akpm@linux-foundation.org>, Andrey Ryabinin <aryabinin@virtuozzo.com>, Andy Shevchenko <andriy.shevchenko@linux.intel.com>, Christoph Hellwig <hch@lst.de>, Daniel Mentz <danielmentz@google.com>, Dmitry Vyukov <dvyukov@google.com>, Geert Uytterhoeven <geert@linux-m68k.org>, Lars Ellenberg <lars.ellenberg@linbit.com>, "Luis R. Rodriguez" <mcgrof@kernel.org>, Marek Szyprowski <m.szyprowski@samsung.com>, Mathieu Desnoyers <mathieu.desnoyers@efficios.com>, Philipp Reisner <philipp.reisner@linbit.com>, Robin Murphy <robin.murphy@arm.com>, Will Deacon <will.deacon@arm.com>, LKML <linux-kernel@vger.kernel.org>, kernel-janitors@vger.kernel.org Subject: Re: [PATCH 1/2] lib/test: Delete five error messages for a failed memory allocation Date: Mon, 09 Oct 2017 06:24:39 +0000 [thread overview] Message-ID: <20171009062439.oxocubhhhnd7t23c@dhcp22.suse.cz> (raw) In-Reply-To: <410a4c5a-4ee0-6fcc-969c-103d8e496b78@users.sourceforge.net> On Sat 07-10-17 19:48:37, SF Markus Elfring wrote: > From: Markus Elfring <elfring@users.sourceforge.net> > Date: Sat, 7 Oct 2017 17:34:23 +0200 > > Omit extra messages for a memory allocation failure in these functions. > > This issue was detected by using the Coccinelle software. Yes this makes sense. None of those really explain what the allocation failure effect is. The allocation path already tells us about the failure enough. > Signed-off-by: Markus Elfring <elfring@users.sourceforge.net> Acked-by: Michal Hocko <mhocko@suse.com> > --- > lib/test_kasan.c | 5 ++--- > lib/test_kmod.c | 8 ++------ > lib/test_list_sort.c | 9 +++------ > 3 files changed, 7 insertions(+), 15 deletions(-) > > diff --git a/lib/test_kasan.c b/lib/test_kasan.c > index a25c9763fce1..ef1a3ac1397e 100644 > --- a/lib/test_kasan.c > +++ b/lib/test_kasan.c > @@ -353,10 +353,9 @@ static noinline void __init memcg_accounted_kmem_cache(void) > */ > for (i = 0; i < 5; i++) { > p = kmem_cache_alloc(cache, GFP_KERNEL); > - if (!p) { > - pr_err("Allocation failed\n"); > + if (!p) > goto free_cache; > - } > + > kmem_cache_free(cache, p); > msleep(100); > } > diff --git a/lib/test_kmod.c b/lib/test_kmod.c > index fba78d25e825..337f408b4de6 100644 > --- a/lib/test_kmod.c > +++ b/lib/test_kmod.c > @@ -783,10 +783,8 @@ static int kmod_config_sync_info(struct kmod_test_device *test_dev) > free_test_dev_info(test_dev); > test_dev->info = vzalloc(config->num_threads * > sizeof(struct kmod_test_device_info)); > - if (!test_dev->info) { > - dev_err(test_dev->dev, "Cannot alloc test_dev info\n"); > + if (!test_dev->info) > return -ENOMEM; > - } > > return 0; > } > @@ -1089,10 +1087,8 @@ static struct kmod_test_device *alloc_test_dev_kmod(int idx) > struct miscdevice *misc_dev; > > test_dev = vzalloc(sizeof(struct kmod_test_device)); > - if (!test_dev) { > - pr_err("Cannot alloc test_dev\n"); > + if (!test_dev) > goto err_out; > - } > > mutex_init(&test_dev->config_mutex); > mutex_init(&test_dev->trigger_mutex); > diff --git a/lib/test_list_sort.c b/lib/test_list_sort.c > index 28e817387b04..5474f3f3e41d 100644 > --- a/lib/test_list_sort.c > +++ b/lib/test_list_sort.c > @@ -76,17 +76,14 @@ static int __init list_sort_test(void) > pr_debug("start testing list_sort()\n"); > > elts = kcalloc(TEST_LIST_LEN, sizeof(*elts), GFP_KERNEL); > - if (!elts) { > - pr_err("error: cannot allocate memory\n"); > + if (!elts) > return err; > - } > > for (i = 0; i < TEST_LIST_LEN; i++) { > el = kmalloc(sizeof(*el), GFP_KERNEL); > - if (!el) { > - pr_err("error: cannot allocate memory\n"); > + if (!el) > goto exit; > - } > + > /* force some equivalencies */ > el->value = prandom_u32() % (TEST_LIST_LEN / 3); > el->serial = i; > -- > 2.14.2 -- Michal Hocko SUSE Labs
next prev parent reply other threads:[~2017-10-09 6:24 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-10-07 17:46 [PATCH 0/2] lib: Adjustments for 11 function implementations SF Markus Elfring 2017-10-07 17:46 ` SF Markus Elfring 2017-10-07 17:48 ` [PATCH 1/2] lib/test: Delete five error messages for a failed memory allocation SF Markus Elfring 2017-10-07 17:48 ` SF Markus Elfring 2017-10-09 6:24 ` Michal Hocko [this message] 2017-10-09 6:24 ` Michal Hocko 2017-10-07 17:50 ` [PATCH 2/2] lib: Improve a size determination in seven functions SF Markus Elfring 2017-10-07 17:50 ` SF Markus Elfring 2017-10-08 10:49 ` Geert Uytterhoeven 2017-10-08 10:49 ` Geert Uytterhoeven 2017-10-08 8:42 ` [PATCH 0/2] lib: Adjustments for 11 function implementations Christoph Hellwig 2017-10-08 8:42 ` Christoph Hellwig 2017-10-08 8:42 ` Christoph Hellwig 2017-10-08 14:21 ` Andy Shevchenko 2017-10-08 14:21 ` Andy Shevchenko 2017-10-08 14:21 ` Andy Shevchenko
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=20171009062439.oxocubhhhnd7t23c@dhcp22.suse.cz \ --to=mhocko@kernel.org \ --cc=akpm@linux-foundation.org \ --cc=andriy.shevchenko@linux.intel.com \ --cc=aryabinin@virtuozzo.com \ --cc=danielmentz@google.com \ --cc=dvyukov@google.com \ --cc=elfring@users.sourceforge.net \ --cc=geert@linux-m68k.org \ --cc=glider@google.com \ --cc=hch@lst.de \ --cc=iommu@lists.linux-foundation.org \ --cc=kasan-dev@googlegroups.com \ --cc=kernel-janitors@vger.kernel.org \ --cc=lars.ellenberg@linbit.com \ --cc=linux-kernel@vger.kernel.org \ --cc=m.szyprowski@samsung.com \ --cc=mathieu.desnoyers@efficios.com \ --cc=mcgrof@kernel.org \ --cc=philipp.reisner@linbit.com \ --cc=robin.murphy@arm.com \ --cc=will.deacon@arm.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.