Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Adam Miartus <amiartus@de.adit-jv.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH 0/3] pcm_file report EIO when fail to write to	debug file
Date: Wed, 03 Jul 2019 14:23:59 +0200	[thread overview]
Message-ID: <s5htvc32tnk.wl-tiwai@suse.de> (raw)
In-Reply-To: <1561987518-2828-1-git-send-email-amiartus@de.adit-jv.com>

On Mon, 01 Jul 2019 15:25:15 +0200,
Adam Miartus wrote:
> 
> Previously, I introduced a patch that may return EPIPE error when pcm_file
> plugin fails to write to output file for some reason.
> 
> The purpose of reporting the error was to evade assert in code to allow
> API user error handling and recovery, or more clarity in debugging.
> 
> Failing to write to a file usually means bad file descriptor, running
> out of free memory, insufficient file permissions or in case file
> is a pipe there may be other reasons preventing the write operation.
> All these are not easily recoverable by restaring playback as EPIPE
> error which is used to signal XRUN might suggest. Therefore, use EIO
> to signal a different kind of error.
> 
> write_wav_header function is refactored a bit for more detailed
> error handling in case of failed write operation.
> 
> Adam Miartus (3):
>   pcm_file: use EIO instead of EPIPE when failing to write output file
>   pcm_file: improve error checking in write_wav_header function
>   pcm_file: in case of failed write clear file buffer variables

I applied patches 1 and 3.  Could you resubmit patch 2 after
correction?


thanks,

Takashi

      parent reply	other threads:[~2019-07-03 12:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-01 13:25 [PATCH 0/3] pcm_file report EIO when fail to write to debug file Adam Miartus
2019-07-01 13:25 ` [PATCH 1/3] pcm_file: use EIO instead of EPIPE when failing to write output file Adam Miartus
2019-07-03 12:23   ` Takashi Iwai
2019-07-01 13:25 ` [PATCH 2/3] pcm_file: improve error checking in write_wav_header function Adam Miartus
2019-07-03 12:21   ` Takashi Iwai
2019-07-01 13:25 ` [PATCH 3/3] pcm_file: in case of failed write clear file buffer variables Adam Miartus
2019-07-03 12:23   ` Takashi Iwai
2019-07-03 12:23 ` Takashi Iwai [this message]

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=s5htvc32tnk.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=amiartus@de.adit-jv.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox