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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id EF127C001DC for ; Mon, 17 Jul 2023 14:40:05 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231877AbjGQOkE (ORCPT ); Mon, 17 Jul 2023 10:40:04 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60930 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229603AbjGQOkA (ORCPT ); Mon, 17 Jul 2023 10:40:00 -0400 Received: from smtp-out2.suse.de (smtp-out2.suse.de [195.135.220.29]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5393EC0 for ; Mon, 17 Jul 2023 07:39:58 -0700 (PDT) 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-out2.suse.de (Postfix) with ESMTPS id E50231FDA5; Mon, 17 Jul 2023 14:39:56 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_rsa; t=1689604796; h=from:from: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=Rs9uvcUebUMYsasQ832t98i+yhYyEHbW41JV9UaUcj4=; b=QBXM1k8OERxN0iaIwVOM7k5vhYNab1sinEWQWfyhUl83K/x9qG83y7igJixZYo0pXzkdRI 5HkMcCS+exn3+XJT8TeD1ciqGABcwi54XE0gtVhYEEzIfHl3cXGChEHXcjhR0a5c2RS2RZ FDmEsmwHRLip1xKgrlls4W7GMu2tHp8= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_ed25519; t=1689604796; h=from:from: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=Rs9uvcUebUMYsasQ832t98i+yhYyEHbW41JV9UaUcj4=; b=KGjA6IXE8LIozekVLTJtjAkJ34AIUvQdps2KI5hNIjXUFlrW2wcysOtF5nQqqbWl6GfK9R MJAIbtaXHkBP/pCw== 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 C5D67138F8; Mon, 17 Jul 2023 14:39:56 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id w2FkLrxStWS4dQAAMHmgww (envelope-from ); Mon, 17 Jul 2023 14:39:56 +0000 Date: Mon, 17 Jul 2023 16:41:00 +0200 From: Cyril Hrubis To: kernel test robot Cc: Waiman Long , Juri Lelli , Brent Rowsell , Valentin Schneider , Phil Auld , Vincent Guittot , yu.c.chen@intel.com, Peter Zijlstra , aubrey.li@linux.intel.com, linux-kernel@vger.kernel.org, Steven Rostedt , Ben Segall , Peter Hunt , Ingo Molnar , Mel Gorman , oe-lkp@lists.linux.dev, Daniel Bristot de Oliveira , Dietmar Eggemann , ltp@lists.linux.it, lkp@intel.com Subject: Re: [LTP] [PATCH] sched/core: Use empty mask to reset cpumasks in sched_setaffinity() Message-ID: References: <20230628211637.1679348-1-longman@redhat.com> <202307171539.3d8d0e8-oliver.sang@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <202307171539.3d8d0e8-oliver.sang@intel.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi! > Running tests....... > <<>> > tag=sched_setaffinity01 stime=1689382567 > cmdline="sched_setaffinity01" > contacts="" > analysis=exit > <<>> > tst_test.c:1558: TINFO: Timeout per run is 0h 02m 30s > sched_setaffinity01.c:83: TPASS: sched_setaffinity() failed: EFAULT (14) > sched_setaffinity01.c:73: TFAIL: sched_setaffinity() succeded unexpectedly > tst_test.c:1612: TINFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1 > tst_test.c:1614: TBROK: Test killed! (timeout?) So what the test does is that it sets empty affinity mask to sched_setaffinity() and expects EINVAL. Instead it looks like the call now succeeeds, the test stops getting schedulled and is killed by timeout. -- Cyril Hrubis chrubis@suse.cz