From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from picard.linux.it (picard.linux.it [213.254.12.146]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 7C4D7C05027 for ; Wed, 8 Feb 2023 13:54:20 +0000 (UTC) Received: from picard.linux.it (localhost [IPv6:::1]) by picard.linux.it (Postfix) with ESMTP id 76DF53CC147 for ; Wed, 8 Feb 2023 14:54:18 +0100 (CET) Received: from in-6.smtp.seeweb.it (in-6.smtp.seeweb.it [IPv6:2001:4b78:1:20::6]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384)) (No client certificate requested) by picard.linux.it (Postfix) with ESMTPS id 506963CB0FC for ; Wed, 8 Feb 2023 14:54:08 +0100 (CET) Received: from smtp-out1.suse.de (smtp-out1.suse.de [195.135.220.28]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by in-6.smtp.seeweb.it (Postfix) with ESMTPS id 723631400206 for ; Wed, 8 Feb 2023 14:54:07 +0100 (CET) Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out1.suse.de (Postfix) with ESMTPS id B835D34254; Wed, 8 Feb 2023 13:54:06 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_rsa; t=1675864446; h=from:from:reply-to:reply-to:date:date:message-id:message-id:to:to: cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=KXjxEl+uh7obsGy3D0zS6upxX1s0mU9rSJQV6E2zsUM=; b=xo5OUdEDh5kk8NX2yaxoSfOR2+WigGmncM4VxcpCUn/rnMnlCSmu4DU9OqAj/1JxD61iel HWsp619SgAieFHSwnfoqrlXstvSRnEWfRgtvCIZykA4A952lvzFMBf2ssIC+KE04HWhi6n DTMJ6n/DDJ9GXt38rbTM2NJq0N/l0Ew= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_ed25519; t=1675864446; h=from:from:reply-to:reply-to:date:date:message-id:message-id:to:to: cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=KXjxEl+uh7obsGy3D0zS6upxX1s0mU9rSJQV6E2zsUM=; b=0n5XO0afQqdAT/SSXMw1zPhphr9cXyTg02quIvACDhlrZizfmd8EQXKtIC2VZbVUQcgY6q qKWUB7z17pYgj6Aw== Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id A003E1358A; Wed, 8 Feb 2023 13:54:06 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id ulkhJn6p42PCEwAAMHmgww (envelope-from ); Wed, 08 Feb 2023 13:54:06 +0000 Date: Wed, 8 Feb 2023 14:54:05 +0100 From: Petr Vorel To: Li Wang Message-ID: <20230208135404.GB31469@pevik> References: <20230207131714.2500-1-pvorel@suse.cz> <20230207131714.2500-2-pvorel@suse.cz> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-Virus-Scanned: clamav-milter 0.102.4 at in-6.smtp.seeweb.it X-Virus-Status: Clean Subject: Re: [LTP] [PATCH 1/3] ioctl01: Add default tty device X-BeenThere: ltp@lists.linux.it X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux Test Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Petr Vorel Cc: ltp@lists.linux.it Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ltp-bounces+ltp=archiver.kernel.org@lists.linux.it Sender: "ltp" Hi Li, > > +#define DEFAULT_TTY_DEVICE "/dev/tty0" > Hidden the device path parameter is a good idea. > But maybe can we add a function to find available char devices instead > of using the tty0 as default? In that function, we do the S_ISCHR() check > and return the valid path of it. Then the rest test (e.g. ioctl02) can make > use of it but not set the specified device as well. WDYT? FYI I'm using S_ISCHR() in other patches, which check if device can be used. Implementing search looks like a good idea. Are useful files any /dev/tty* (including /dev/tty, /dev/ttyACM0, /dev/ttyS0) or should I avoid any file or include other paths? Kind regards, Petr -- Mailing list info: https://lists.linux.it/listinfo/ltp