All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mikulas Patocka <mpatocka@redhat.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, dm-devel@redhat.com,
	Zdenek Kabelac <zkabelac@redhat.com>,
	ming.lei@redhat.com
Subject: [PATCH] block: remove the "detected capacity change" message
Date: Wed, 17 Mar 2021 06:46:49 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LRH.2.02.2103170644080.32577@file01.intranet.prod.int.rdu2.redhat.com> (raw)

Every time a new device mapper device is created, a message "detected
capacity change from 0 to 2097152" is reported. This message is useless,
so this patch removes it.

Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>

---
 block/genhd.c |    3 ---
 1 file changed, 3 deletions(-)

Index: linux-2.6/block/genhd.c
===================================================================
--- linux-2.6.orig/block/genhd.c	2021-03-17 11:03:52.000000000 +0100
+++ linux-2.6/block/genhd.c	2021-03-17 11:04:27.000000000 +0100
@@ -72,9 +72,6 @@ bool set_capacity_and_notify(struct gend
 	    (disk->flags & (GENHD_FL_UP | GENHD_FL_HIDDEN)) != GENHD_FL_UP)
 		return false;
 
-	pr_info("%s: detected capacity change from %lld to %lld\n",
-		disk->disk_name, capacity, size);
-
 	/*
 	 * Historically we did not send a uevent for changes to/from an empty
 	 * device.


WARNING: multiple messages have this Message-ID (diff)
From: Mikulas Patocka <mpatocka@redhat.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, dm-devel@redhat.com,
	ming.lei@redhat.com, Zdenek Kabelac <zkabelac@redhat.com>
Subject: [dm-devel] [PATCH] block: remove the "detected capacity change" message
Date: Wed, 17 Mar 2021 06:46:49 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LRH.2.02.2103170644080.32577@file01.intranet.prod.int.rdu2.redhat.com> (raw)

Every time a new device mapper device is created, a message "detected
capacity change from 0 to 2097152" is reported. This message is useless,
so this patch removes it.

Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>

---
 block/genhd.c |    3 ---
 1 file changed, 3 deletions(-)

Index: linux-2.6/block/genhd.c
===================================================================
--- linux-2.6.orig/block/genhd.c	2021-03-17 11:03:52.000000000 +0100
+++ linux-2.6/block/genhd.c	2021-03-17 11:04:27.000000000 +0100
@@ -72,9 +72,6 @@ bool set_capacity_and_notify(struct gend
 	    (disk->flags & (GENHD_FL_UP | GENHD_FL_HIDDEN)) != GENHD_FL_UP)
 		return false;
 
-	pr_info("%s: detected capacity change from %lld to %lld\n",
-		disk->disk_name, capacity, size);
-
 	/*
 	 * Historically we did not send a uevent for changes to/from an empty
 	 * device.

--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel


             reply	other threads:[~2021-03-17 10:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-17 10:46 Mikulas Patocka [this message]
2021-03-17 10:46 ` [dm-devel] [PATCH] block: remove the "detected capacity change" message Mikulas Patocka
2021-03-17 13:47 ` Christoph Hellwig
2021-03-17 13:47   ` [dm-devel] " Christoph Hellwig
2021-03-17 15:34   ` Mikulas Patocka
2021-03-17 15:34     ` [dm-devel] " Mikulas Patocka

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=alpine.LRH.2.02.2103170644080.32577@file01.intranet.prod.int.rdu2.redhat.com \
    --to=mpatocka@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=dm-devel@redhat.com \
    --cc=linux-block@vger.kernel.org \
    --cc=ming.lei@redhat.com \
    --cc=zkabelac@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 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.