From: Tony Asleson <tasleson@redhat.com>
To: linux-scsi@vger.kernel.org, linux-block@vger.kernel.org
Subject: [RFC PATCH v3 2/8] create_syslog_header: Add durable name
Date: Tue, 23 Jun 2020 14:17:43 -0500 [thread overview]
Message-ID: <20200623191749.115200-3-tasleson@redhat.com> (raw)
In-Reply-To: <20200623191749.115200-1-tasleson@redhat.com>
This gets us a persistent durable name for code that logs messages in the
block layer that have the appropriate callbacks setup for durable name.
Signed-off-by: Tony Asleson <tasleson@redhat.com>
---
drivers/base/core.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/drivers/base/core.c b/drivers/base/core.c
index 511b7d2fc916..964690572a89 100644
--- a/drivers/base/core.c
+++ b/drivers/base/core.c
@@ -3754,6 +3754,7 @@ create_syslog_header(const struct device *dev, char *hdr, size_t hdrlen)
{
const char *subsys;
size_t pos = 0;
+ int dlen;
if (dev->class)
subsys = dev->class->name;
@@ -3796,6 +3797,10 @@ create_syslog_header(const struct device *dev, char *hdr, size_t hdrlen)
"DEVICE=+%s:%s", subsys, dev_name(dev));
}
+ dlen = dev_durable_name(dev, hdr + (pos + 1), hdrlen - (pos + 1));
+ if (dlen)
+ pos += dlen + 1;
+
if (pos >= hdrlen)
goto overflow;
--
2.25.4
next prev parent reply other threads:[~2020-06-23 19:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 19:17 [RFC PATCH v3 0/8] Add persistent durable identifier to storage log messages Tony Asleson
2020-06-23 19:17 ` [RFC PATCH v3 1/8] struct device: Add function callback durable_name Tony Asleson
2020-06-23 19:17 ` Tony Asleson [this message]
2020-06-23 19:17 ` [RFC PATCH v3 3/8] print_req_error: Use dev_printk Tony Asleson
2020-06-23 19:17 ` [RFC PATCH v3 4/8] buffer_io_error: " Tony Asleson
2020-06-23 19:17 ` [RFC PATCH v3 5/8] ata_dev_printk: " Tony Asleson
[not found] ` <CGME20200624103532eucas1p2c0988207e4dfc2f992d309b75deac3ee@eucas1p2.samsung.com>
2020-06-24 10:35 ` Bartlomiej Zolnierkiewicz
2020-06-24 15:15 ` Tony Asleson
2020-06-26 12:45 ` Bartlomiej Zolnierkiewicz
2020-06-26 13:54 ` Tony Asleson
[not found] ` <7ed08b94-755f-baab-0555-b4e454405729@redhat.com>
2020-07-14 8:06 ` Bartlomiej Zolnierkiewicz
2020-07-14 8:17 ` Greg Kroah-Hartman
2020-07-14 8:50 ` Bartlomiej Zolnierkiewicz
2020-07-17 10:06 ` Greg Kroah-Hartman
2020-07-17 10:17 ` Hannes Reinecke
2020-07-17 10:27 ` Bartlomiej Zolnierkiewicz
2020-07-17 19:47 ` Tony Asleson
2020-07-24 8:50 ` Bartlomiej Zolnierkiewicz
2020-06-23 19:17 ` [RFC PATCH v3 6/8] scsi: Add durable_name for dev_printk Tony Asleson
2020-06-23 19:17 ` [RFC PATCH v3 7/8] nvme: Add durable name " Tony Asleson
2020-06-23 20:04 ` Chaitanya Kulkarni
2020-06-23 20:32 ` Tony Asleson
2020-06-23 19:17 ` [RFC PATCH v3 8/8] dev_vprintk_emit: Increase hdr size Tony Asleson
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=20200623191749.115200-3-tasleson@redhat.com \
--to=tasleson@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
/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).