From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Subject: [PATCH v2] commands: don't use stale errno when calling fb_open
Date: Tue, 11 Jun 2019 11:12:22 +0200 [thread overview]
Message-ID: <20190611091222.10461-1-a.fatoum@pengutronix.de> (raw)
fb_open returns a pointer and doesn't populate errno, which will
result in a stale errno being evaluated by perror() on failure.
Fix this by using strerror with the proper argument instead at call sites.
While at it, correct the message prefix typo (s/fb_open/fb_open/).
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
Changes since v1:
* use strerror instead of perror/errno as suggested by Andrey & Sascha
* negated PTR_ERR output, so the error is positive
commands/fbtest.c | 5 +++--
commands/splash.c | 5 +++--
2 files changed, 6 insertions(+), 4 deletions(-)
diff --git a/commands/fbtest.c b/commands/fbtest.c
index e5dd8ba7fabf..ff24a8252a8c 100644
--- a/commands/fbtest.c
+++ b/commands/fbtest.c
@@ -271,8 +271,9 @@ static int do_fbtest(int argc, char *argv[])
sc = fb_open(fbdev);
if (IS_ERR(sc)) {
- perror("fd_open");
- return PTR_ERR(sc);
+ int ret = -PTR_ERR(sc);
+ printf("fb_open: %s\n", strerror(ret));
+ return ret;
}
if (!pattern_name) {
diff --git a/commands/splash.c b/commands/splash.c
index 2b70b296837e..abd82873cb6d 100644
--- a/commands/splash.c
+++ b/commands/splash.c
@@ -54,8 +54,9 @@ static int do_splash(int argc, char *argv[])
sc = fb_open(fbdev);
if (IS_ERR(sc)) {
- perror("fd_open");
- return PTR_ERR(sc);
+ int ret = -PTR_ERR(sc);
+ printf("fb_open: %s\n", strerror(ret));
+ return ret;
}
buf = gui_screen_render_buffer(sc);
--
2.20.1
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2019-06-11 9:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 9:12 Ahmad Fatoum [this message]
2019-06-13 6:15 ` Sascha Hauer
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=20190611091222.10461-1-a.fatoum@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.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