linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: weiping zhang <zhangweiping@didichuxing.com>
To: Bruno Wolff III <bruno@wolff.to>
Cc: Laura Abbott <labbott@redhat.com>, Jan Kara <jack@suse.cz>,
	Jens Axboe <axboe@kernel.dk>, <linux-mm@kvack.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	<regressions@leemhuis.info>, <linux-block@vger.kernel.org>
Subject: Re: Regression with a0747a859ef6 ("bdi: add error handle for bdi_debug_register")
Date: Thu, 14 Dec 2017 18:09:27 +0800	[thread overview]
Message-ID: <20171214100927.GA26167@localhost.didichuxing.com> (raw)
In-Reply-To: <20171214082452.GA16698@wolff.to>

On Thu, Dec 14, 2017 at 02:24:52AM -0600, Bruno Wolff III wrote:
> On Wed, Dec 13, 2017 at 16:54:17 -0800,
>  Laura Abbott <labbott@redhat.com> wrote:
> >Hi,
> >
> >Fedora got a bug report https://bugzilla.redhat.com/show_bug.cgi?id=1520982
> >of a boot failure/bug on Linus' master (full bootlog at the bugzilla)
> 
> I'm available for testing. The problem happens on my x86_64 Dell
> Workstation, but not an old i386 server or an x86_64 mac hardware
> based laptop.

Hi,

It seems something wrong with bdi debugfs register, could you help
test the forllowing debug patch, I add some debug log, no function
change, thanks.


>From d2728c07589e8b83115a51e0c629451bff7308db Mon Sep 17 00:00:00 2001
From: weiping zhang <zhangweiping@didichuxing.com>
Date: Thu, 14 Dec 2017 17:56:22 +0800
Subject: [PATCH] bdi debugfs

Signed-off-by: weiping zhang <zhangweiping@didichuxing.com>
---
 mm/backing-dev.c | 28 +++++++++++++++++++++++++---
 1 file changed, 25 insertions(+), 3 deletions(-)

diff --git a/mm/backing-dev.c b/mm/backing-dev.c
index 84b2dc7..fbbb9a6 100644
--- a/mm/backing-dev.c
+++ b/mm/backing-dev.c
@@ -39,6 +39,10 @@ static struct dentry *bdi_debug_root;
 static void bdi_debug_init(void)
 {
 	bdi_debug_root = debugfs_create_dir("bdi", NULL);
+	if (!bdi_debug_root)
+		pr_err("DEBUG:bdi_debug_root fail\n");
+	else
+		pr_err("DEBUG:bdi_debug_root success\n");
 }
 
 static int bdi_debug_stats_show(struct seq_file *m, void *v)
@@ -115,18 +119,29 @@ static const struct file_operations bdi_debug_stats_fops = {
 
 static int bdi_debug_register(struct backing_dev_info *bdi, const char *name)
 {
-	if (!bdi_debug_root)
+	if (!bdi_debug_root) {
+		pr_err("DEBUG:dev:%s, bdi_debug_root fail\n", name);
 		return -ENOMEM;
+	} else {
+		pr_err("DEBUG:dev:%s, bdi_debug_root success\n", name);
+	}
 
 	bdi->debug_dir = debugfs_create_dir(name, bdi_debug_root);
-	if (!bdi->debug_dir)
+	if (!bdi->debug_dir) {
+		pr_err("DEBUG:dev:%s, debug_dir fail\n", name);
 		return -ENOMEM;
+	} else {
+		pr_err("DEBUG:dev:%s, debug_dir success\n", name);
+	}
 
 	bdi->debug_stats = debugfs_create_file("stats", 0444, bdi->debug_dir,
 					       bdi, &bdi_debug_stats_fops);
 	if (!bdi->debug_stats) {
 		debugfs_remove(bdi->debug_dir);
+		pr_err("DEBUG:dev:%s, debug_stats fail\n", name);
 		return -ENOMEM;
+	} else {
+		pr_err("DEBUG:dev:%s, debug_stats success\n", name);
 	}
 
 	return 0;
@@ -879,13 +894,20 @@ int bdi_register_va(struct backing_dev_info *bdi, const char *fmt, va_list args)
 		return 0;
 
 	dev = device_create_vargs(bdi_class, NULL, MKDEV(0, 0), bdi, fmt, args);
-	if (IS_ERR(dev))
+	if (IS_ERR(dev)) {
+		pr_err("DEBUG: bdi device_create_vargs fail\n");
 		return PTR_ERR(dev);
+	}
+	pr_err("DEBUG: bdi(0x%p) device_create_vargs sucess\n", bdi);
 
 	if (bdi_debug_register(bdi, dev_name(dev))) {
+		pr_err("DEBUG: dev:%s, bdi(0x%p) bdi_debug_register fail\n",
+			dev_name(dev), bdi);
 		device_destroy(bdi_class, dev->devt);
 		return -ENOMEM;
 	}
+	pr_err("DEBUG: dev:%s, bdi(0x%p) bdi_debug_register success\n",
+		dev_name(dev), bdi);
 	cgwb_bdi_register(bdi);
 	bdi->dev = dev;
 
-- 
2.9.4

  reply	other threads:[~2017-12-14 10:24 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-14  0:54 Regression with a0747a859ef6 ("bdi: add error handle for bdi_debug_register") Laura Abbott
2017-12-14  8:24 ` Bruno Wolff III
2017-12-14 10:09   ` weiping zhang [this message]
2017-12-14 10:29     ` Bruno Wolff III
2017-12-14 15:41     ` Bruno Wolff III
2017-12-15  1:22       ` weiping zhang
2017-12-15  1:44         ` Bruno Wolff III
2017-12-15  2:04           ` weiping zhang
2017-12-15  2:11             ` Bruno Wolff III
2017-12-15 11:10             ` Bruno Wolff III
2017-12-15 14:02               ` weiping zhang
2017-12-15 16:30                 ` Bruno Wolff III
2017-12-15 17:18                   ` Laura Abbott
2017-12-15 17:40                     ` Bruno Wolff III
2017-12-15 19:51                 ` Bruno Wolff III
2017-12-16 16:32                   ` Bruno Wolff III
2017-12-17 13:43                     ` weiping zhang
2017-12-17 15:54                       ` Bruno Wolff III
2017-12-18 21:53                       ` Bruno Wolff III
2017-12-19 16:17                       ` Bruno Wolff III
2017-12-19 18:24                         ` Shaohua Li
2017-12-19 19:48                           ` Bruno Wolff III
2017-12-20  0:20                           ` Bruno Wolff III
2017-12-21 13:00 ` Bruno Wolff III
2017-12-21 14:01   ` weiping zhang
2017-12-21 15:18     ` Bruno Wolff III
2017-12-21 15:31       ` weiping zhang
2017-12-21 15:36         ` Bruno Wolff III
2017-12-21 15:48           ` weiping zhang
2017-12-21 16:42             ` Bruno Wolff III
2017-12-21 17:02               ` Jens Axboe
2017-12-21 17:46                 ` weiping zhang
2017-12-21 18:15                 ` Bruno Wolff III
2017-12-21 23:16                   ` Bruno Wolff III
2017-12-22  4:53                     ` Bruno Wolff III
2017-12-22 13:20                       ` weiping zhang
2017-12-22 14:04                         ` Bruno Wolff III
2017-12-29 16:30                           ` weiping zhang
2017-12-29 18:44                             ` Bruno Wolff III
2017-12-29 16:36                           ` weiping zhang
2017-12-22  0:29                 ` James Bottomley

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=20171214100927.GA26167@localhost.didichuxing.com \
    --to=zhangweiping@didichuxing.com \
    --cc=axboe@kernel.dk \
    --cc=bruno@wolff.to \
    --cc=jack@suse.cz \
    --cc=labbott@redhat.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=regressions@leemhuis.info \
    /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;
as well as URLs for NNTP newsgroup(s).