public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Michal Privoznik <mprivozn@redhat.com>
Cc: passt-dev@passt.top, sbrivio@redhat.com
Subject: Re: [PATCH] seccomp.sh: Silence stty errors
Date: Mon, 24 Feb 2025 13:05:40 +1100	[thread overview]
Message-ID: <Z7vT9LrBB6VCJom5@zatzit> (raw)
In-Reply-To: <f08a8690f12711ea22154fa7dbcda24d16e7b492.1740138676.git.mprivozn@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 2016 bytes --]

On Fri, Feb 21, 2025 at 12:53:13PM +0100, Michal Privoznik wrote:
> When printing list of allowed syscalls the width of terminal is
> obtained for nicer output (see commit below). The width is
> obtained by running 'stty'. While this works when building from a
> console, it doesn't work during rpmbuild/emerge/.. as stdout is
> usually not a console but a logfile and stdin is usually
> /dev/null or something. This results in stty reporting errors
> like this:
> 
>   stty: 'standard input': Inappropriate ioctl for device
> 
> Redirect stty's stderr to /dev/null to silence it.
> 
> Fixes: 712ca3235329b049bf9a4e481ba38a4c64768e8b
> Signed-off-by: Michal Privoznik <mprivozn@redhat.com>

Reviewed-by: David Gibson <david@gibson.dropbear.id.au>

Although, I also wonder if we'd do just as well to use the shell
provided $COLUMNS variable without poking at the terminal ourselves.

> ---
> 
> I've noticed the error when running emerge on my local system, but then
> also found it on a recent koji build:
> 
> https://kojipkgs.fedoraproject.org//packages/passt/0%5E20250217.ga1e48a0/2.fc41/data/logs/x86_64/build.log
> 
>  seccomp.sh | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/seccomp.sh b/seccomp.sh
> index 4c521ae..a7bc417 100755
> --- a/seccomp.sh
> +++ b/seccomp.sh
> @@ -255,7 +255,7 @@ for __p in ${__profiles}; do
>  	__calls="${__calls} ${EXTRA_SYSCALLS:-}"
>  	__calls="$(filter ${__calls})"
>  
> -	cols="$(stty -a | sed -n 's/.*columns \([0-9]*\).*/\1/p' || :)" 2>/dev/null
> +	cols="$(stty -a 2>/dev/null | sed -n 's/.*columns \([0-9]*\).*/\1/p' || :)" 2>/dev/null
>  	case $cols in [0-9]*) col_args="-w ${cols}";; *) col_args="";; esac
>  	echo "seccomp profile ${__p} allows: ${__calls}" | tr '\n' ' ' | fmt -t ${col_args}
>  

-- 
David Gibson (he or they)	| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you, not the other way
				| around.
http://www.ozlabs.org/~dgibson

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2025-02-24  2:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-21 11:53 [PATCH] seccomp.sh: Silence stty errors Michal Privoznik
2025-02-24  2:05 ` David Gibson [this message]
2025-02-24  7:38   ` Stefano Brivio
2025-02-24  7:41     ` David Gibson
2025-02-24 19:37 ` Stefano Brivio

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=Z7vT9LrBB6VCJom5@zatzit \
    --to=david@gibson.dropbear.id.au \
    --cc=mprivozn@redhat.com \
    --cc=passt-dev@passt.top \
    --cc=sbrivio@redhat.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.
Code repositories for project(s) associated with this public inbox

	https://passt.top/passt

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 IMAP folder(s).