All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Heimpold <mhei@heimpold.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] fix: fw_env: Prevent writing error message on special files, which don't support fsync
Date: Sun, 27 Aug 2017 20:34:12 +0200	[thread overview]
Message-ID: <2356808.ZoFJpPEoSj@kerker> (raw)
In-Reply-To: <1503834382-19583-1-git-send-email-lukma@denx.de>

Hi Lukasz,

Am Sonntag, 27. August 2017, 13:46:22 CEST schrieb Lukasz Majewski:
> According to fsync specification [1] some special files (e.g., a pipe, FIFO,
> or socket) don't support synchronization and return either EROFS or EINVAL.
> 
> On the linux side the sys_fsync -> do_fsync() checks if the requested file
> has f_op->fsync defined. If not it returns EINVAL [2].
> 
> This commit prevents writing error messages for files (devices), which
> do not support fsync().
> 
> [1] - http://man7.org/linux/man-pages/man2/fsync.2.html
> [2] - http://elixir.free-electrons.com/linux/v4.13-rc6/source/fs/sync.c#L183
> 
> Signed-off-by: Lukasz Majewski <lukma@denx.de>
> ---
>  tools/env/fw_env.c | 6 ++++--
>  1 file changed, 4 insertions(+), 2 deletions(-)
> 
> diff --git a/tools/env/fw_env.c b/tools/env/fw_env.c
> index c9c79e0..ab7d85b 100644
> --- a/tools/env/fw_env.c
> +++ b/tools/env/fw_env.c
> @@ -1088,14 +1088,16 @@ static int flash_io (int mode)
> 
>  		rc = flash_write (fd_current, fd_target, dev_target);
> 
> -		if (fsync (fd_current)) {
> +		if (fsync(fd_current) &&

nitpick: current coding style seems to be a single whitespace before
the opening bracket

> +		    !(errno == EINVAL || errno == EROFS)) {
>  			fprintf (stderr,
>  				 "fsync failed on %s: %s\n",
>  				 DEVNAME (dev_current), strerror (errno));
>  		}
> 
>  		if (HaveRedundEnv) {
> -			if (fsync (fd_target)) {
> +			if (fsync(fd_target) &&

dito

> +			    !(errno == EINVAL || errno == EROFS)) {
>  				fprintf (stderr,
>  					 "fsync failed on %s: %s\n",
>  					 DEVNAME (dev_current), strerror (errno));

Other than this nitpick:

Acked-by: Michael Heimpold <mhei@heimpold.de>

Regards,
Michael

  reply	other threads:[~2017-08-27 18:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-27 11:46 [U-Boot] [PATCH] fix: fw_env: Prevent writing error message on special files, which don't support fsync Lukasz Majewski
2017-08-27 18:34 ` Michael Heimpold [this message]
2017-08-27 19:20   ` Łukasz Majewski
2017-08-27 20:01     ` Tom Rini
2017-09-04  0:42 ` [U-Boot] " Tom Rini

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=2356808.ZoFJpPEoSj@kerker \
    --to=mhei@heimpold.de \
    --cc=u-boot@lists.denx.de \
    /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.