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 E1083C61DA4 for ; Thu, 2 Feb 2023 14:59:48 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231904AbjBBO7q (ORCPT ); Thu, 2 Feb 2023 09:59:46 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39394 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232096AbjBBO7o (ORCPT ); Thu, 2 Feb 2023 09:59:44 -0500 Received: from mail-vs1-xe2c.google.com (mail-vs1-xe2c.google.com [IPv6:2607:f8b0:4864:20::e2c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 405B62685 for ; Thu, 2 Feb 2023 06:59:43 -0800 (PST) Received: by mail-vs1-xe2c.google.com with SMTP id h19so2077934vsv.13 for ; Thu, 02 Feb 2023 06:59:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=+oLCarSnbWm9l30IqXlSlJbB/Sspgw6Lli8fZQqOL3w=; b=lR42T0OOHxZom/O2kIv5W9S/umO0DLaJuzIMSW1lHstX3IXJQKC4aY2Cdx7zkx1DyH z/7Y7tLkZWBAHncNZcx0qJ0qd/+8PhEcBVTXgg691A7migWn0lvZiAw+WoS43M9yYAOF pKgvsnCxdzXNJQZaeHx61h3hwrKL+kgcW0ylndtg2+iHNlQcgfQS7EZ1O9rKyuP+yl60 gYyNyfL3b7TMRhr7wJ5qIJH6uMrPkYwLGXEiu2UGAl3uDqHCHHJBK5nRqUFkSuPXQFmP a6WEJ+6uz2xEjAdnYbRTViz88rdB1pDnEQYM8pAoVRPvA27pryAGHnM7j7PgkgmG7GZB /CSw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=+oLCarSnbWm9l30IqXlSlJbB/Sspgw6Lli8fZQqOL3w=; b=QwRJgGj5I6bDZVUt9uGdhIr1d8P6QmConhh7btYMFRWf2TdEKIY+dOc4l54iEdC599 WnEl49YXplnctoYea7cXZRByG2Xp99KRnjSwXQVFhIo6mTrrdO/Z5GRukh98vvPANKev 4QRfLG27Qsi7e/wP413yGi2sgBWJ5z30uB8PhAnZQYXJJ03GLVfhMTmAV6bt/fSY9gDe 8oaVMPdleCXTFIsAmOjTIDHmdBeSae3A1i1qkyLiHaMaM+RKiuFplbbgm2V+j5KimUj5 axAaEXJSGoIn/AehANJq8FbyMdPA+7UNrfcEqRfXzZ/B3RpD0+JipRPmaC5VAbTb3pWb tLzA== X-Gm-Message-State: AO0yUKXfwO2P0AMGGH5PL4JpZ1NRylTvdu2KnPB+h9oeSTrBV47a5pZt 3TVY6eY/O0Q92F22mWe/Hagprn4SCfKYuVLnZ9DS4w== X-Google-Smtp-Source: AK7set/1VTblN/hGaphDW8ItFDqXbRBBkClqYBuZ91ZzszVwUlVtqXARv4RqxlDHHu+pSqXWJ80Yrhc7dPyfKyi7MUk= X-Received: by 2002:a05:6102:3ce:b0:3f0:f82a:1f8c with SMTP id n14-20020a05610203ce00b003f0f82a1f8cmr970844vsq.74.1675349982148; Thu, 02 Feb 2023 06:59:42 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Naresh Kamboju Date: Thu, 2 Feb 2023 20:29:31 +0530 Message-ID: Subject: Re: selftests: memfd: run_hugetlbfs_test.sh - invalid opcode: 0000 [#1] PREEMPT SMP To: Mike Kravetz Cc: "open list:KERNEL SELFTEST FRAMEWORK" , open list , linux-stable , lkft-triage@lists.linaro.org, Greg Kroah-Hartman , Andrew Morton , Shuah Khan , Jeff Xu , Joel Fernandes , Pranith Kumar , David Herrmann Content-Type: multipart/mixed; boundary="0000000000009008a505f3b8d0e1" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --0000000000009008a505f3b8d0e1 Content-Type: text/plain; charset="UTF-8" [Resending because logs.txt attachment was not successful ] Hi Mike, On Wed, 25 Jan 2023 at 06:04, Mike Kravetz wrote: > > On 01/05/23 15:14, Naresh Kamboju wrote: > > While running selftests: memfd: run_hugetlbfs_test.sh on qemu_i386 and i386 the > > following invalid opcode was noticed on stable-rc 6.1 and 6.0. > > > > This is always reproducible on stable-rc 6.1 and 6.0 with qemu_i386 and i386. > > Build, config and test log details provided in the below links [1]. > > Hello Naresh, > > I have tried to create this issue a few times without success. Since I > do not have i386 HW, I am using qemu_i386. If I use the supplied config, > my kernel does not boot. I then try to modify config options which I > think are not relevant. By the time I get to a config that will boot, I > can not recreate the issue. :( > > Just curious if you have any suggestions? Or, Wondering if anyone else has > suggestions on how to proceed? Please install tuxmake and run attached script to reproduce reported issues, $ pip3 install tuxmake $ ./memfd-crash-test-qemu-i386.sh This script downloads kernel Image and rootfs and runs run_hugetlbfs_test.sh. If you have any questions please get back to me. ref: https://tuxsuite.com/ > -- > Mike Kravetz --0000000000009008a505f3b8d0e1 Content-Type: application/x-shellscript; name="memfd-crash-test-qemu-i386.sh" Content-Disposition: attachment; filename="memfd-crash-test-qemu-i386.sh" Content-Transfer-Encoding: base64 Content-ID: X-Attachment-Id: f_ldn82ilt0 dHV4cnVuIC0tcnVudGltZSBwb2RtYW4gLS1kZXZpY2UgcWVtdS1pMzg2IC0ta2VybmVsIGh0dHBz Oi8vc3RvcmFnZS50dXhzdWl0ZS5jb20vcHVibGljL2xpbmFyby9sa2Z0L2J1aWxkcy8ySnJ6dlpj MjIzcGN0bEF4VmhDSWViSjhxMHcvYnpJbWFnZSAtLW1vZHVsZXMgaHR0cHM6Ly9zdG9yYWdlLnR1 eHN1aXRlLmNvbS9wdWJsaWMvbGluYXJvL2xrZnQvYnVpbGRzLzJKcnp2WmMyMjNwY3RsQXhWaENJ ZWJKOHEwdy9tb2R1bGVzLnRhci54eiAtLXJvb3RmcyBodHRwczovL3N0b3JhZ2UudHV4Ym9vdC5j b20vZGViaWFuL2Jvb2t3b3JtL2kzODYvcm9vdGZzLmV4dDQueHogLS1wYXJhbWV0ZXJzIFNLSVBG SUxFPXNraXBmaWxlLWxrZnQueWFtbCAtLXNhdmUtb3V0cHV0IC0tbG9nLWZpbGUgLSAtLWJvb3Qt YXJncyBydyAtLW92ZXJsYXkgaHR0cHM6Ly9zdG9yYWdlLnR1eHN1aXRlLmNvbS9wdWJsaWMvbGlu YXJvL2xrZnQvYnVpbGRzLzJKcnp2WmMyMjNwY3RsQXhWaENJZWJKOHEwdy9rc2VsZnRlc3QudGFy Lnh6IC0tICdjZCAvbWVtZmQgJiYgLi9ydW5faHVnZXRsYmZzX3Rlc3Quc2gnCgo= --0000000000009008a505f3b8d0e1--