Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 6E5325685 for ; Tue, 7 Feb 2023 17:26:39 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1675790798; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=A1UvW0wrHQWigj5Ouf4r26jfQmoM0gSCL18qsIrw6jw=; b=IV/F7MMQ9nZaN88vHBpbdl9vKxVMnNU5ifiypG2uWnu7KnheUDUugJa055meV2m3mi65X+ IBGr++eTAcAm6ARHEgySdT9+500/As0dBp0JU3LhfaAvigqk3K0mdQoe+wBmqqmhAXB/Em lH5iIVdLLpdgInJDDJu9dgv2KtsZN2M= Received: from mail-qk1-f200.google.com (mail-qk1-f200.google.com [209.85.222.200]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-416-YnvstaEWMyq_FektsMz5ig-1; Tue, 07 Feb 2023 12:26:36 -0500 X-MC-Unique: YnvstaEWMyq_FektsMz5ig-1 Received: by mail-qk1-f200.google.com with SMTP id op32-20020a05620a536000b0072e2c4dea65so8387683qkn.12 for ; Tue, 07 Feb 2023 09:26:36 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-transfer-encoding:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=A1UvW0wrHQWigj5Ouf4r26jfQmoM0gSCL18qsIrw6jw=; b=OcoFCATOCwFJ/N1uV3pKj4vtlpYRhsjWK+EayaNosdmfcSrXX4svs6ENf+b4/rF2sn oZTLUPmcsPD+veP2nFgo2zUvJI/eCmi+PBu+tgJ/qV0Q2bBrjvsatNEkEoppLC/2qffo +2FA9Nx/0pyEV554+bcD4NaJU+5x0posQnZj5eWk2GvsyElPq2lzDEuygH2KLmVLyGhu JQhbW4vzj3sEzun3KNmE3tiAnzsSSJwJHcegR4tM1qMBQpiBcgcCcevqOOMdcxcKiAL8 hC4fiC+8DIOoTIVQ40ixSZRCcXZPwvoc/T7EIRnVGtlZlrudKCiLWgq5/D7I5w8eJK6o Hp5w== X-Gm-Message-State: AO0yUKX2vi4+XdtAjpGR+Y5FeSJLH+r2Mv0svMnX/0LiNeibscSKfV/S YtdUBggy+hQGw0s6OGbsSJTY3W6Nr0Z/jWZu8LoaO0CXX1Qhd2vvl3OeFPM2gjxgcICSoG88buC YDKBDriGRefQ1RXeANA== X-Received: by 2002:ac8:5f4a:0:b0:3b8:6801:90b3 with SMTP id y10-20020ac85f4a000000b003b8680190b3mr8018607qta.0.1675790796174; Tue, 07 Feb 2023 09:26:36 -0800 (PST) X-Google-Smtp-Source: AK7set+G8xGUvyalZMLlK6nlAAPgyJL+bwcDkz+CtGrVcO3QWHRQv0maEwKkbLk5D0mzcwb/8BJN8A== X-Received: by 2002:ac8:5f4a:0:b0:3b8:6801:90b3 with SMTP id y10-20020ac85f4a000000b003b8680190b3mr8018567qta.0.1675790795820; Tue, 07 Feb 2023 09:26:35 -0800 (PST) Received: from x1n (bras-base-aurron9127w-grc-56-70-30-145-63.dsl.bell.ca. [70.30.145.63]) by smtp.gmail.com with ESMTPSA id j24-20020a37ef18000000b0072396cb73cdsm9781553qkk.13.2023.02.07.09.26.34 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 07 Feb 2023 09:26:35 -0800 (PST) Date: Tue, 7 Feb 2023 12:26:33 -0500 From: Peter Xu To: Naresh Kamboju Cc: Greg Kroah-Hartman , stable@vger.kernel.org, patches@lists.linux.dev, linux-kernel@vger.kernel.org, torvalds@linux-foundation.org, akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org, patches@kernelci.org, lkft-triage@lists.linaro.org, pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com, sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de, Mike Kravetz , Jann Horn , Anders Roxell , "open list:KERNEL SELFTEST FRAMEWORK" Subject: Re: [PATCH 6.1 000/208] 6.1.11-rc1 review Message-ID: References: <20230207125634.292109991@linuxfoundation.org> Precedence: bulk X-Mailing-List: patches@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 In-Reply-To: X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit On Tue, Feb 07, 2023 at 10:35:19PM +0530, Naresh Kamboju wrote: > On Tue, 7 Feb 2023 at 18:29, Greg Kroah-Hartman > wrote: > > > > This is the start of the stable review cycle for the 6.1.11 release. > > There are 208 patches in this series, all will be posted as a response > > to this one. If anyone has any issues with these being applied, please > > let me know. > > > > Responses should be made by Thu, 09 Feb 2023 12:55:54 +0000. > > Anything received after that time might be too late. > > > > The whole patch series can be found in one patch at: > > https://www.kernel.org/pub/linux/kernel/v6.x/stable-review/patch-6.1.11-rc1.gz > > or in the git tree and branch at: > > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.1.y > > and the diffstat can be found below. > > > > thanks, > > > > greg k-h > > Results from Linaro’s test farm. > Following build regressions noticed while building > selftests/vm/hugetlb-madvise.c > with kselftest-merge configs. > > Reported-by: Linux Kernel Functional Testing > > Build errors: > ---------- > hugetlb-madvise.c:242:13: warning: implicit declaration of function > 'fallocate'; did you mean 'alloca'? [-Wimplicit-function-declaration] > 242 | if (fallocate(fd, 0, 0, NR_HUGE_PAGES * huge_page_size)) { > | ^~~~~~~~~ > | alloca > hugetlb-madvise.c:289:27: error: 'FALLOC_FL_PUNCH_HOLE' undeclared > (first use in this function) > 289 | if (fallocate(fd, FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE, > | ^~~~~~~~~~~~~~~~~~~~ > hugetlb-madvise.c:289:27: note: each undeclared identifier is reported > only once for each function it appears in > hugetlb-madvise.c:289:50: error: 'FALLOC_FL_KEEP_SIZE' undeclared > (first use in this function) > 289 | if (fallocate(fd, FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE, > | ^~~~~~~~~~~~~~~~~~~ > make[3]: *** [../lib.mk:145: > /home/tuxbuild/.cache/tuxmake/builds/1/build/kselftest/vm/hugetlb-madvise] > Error 1 > > Build log: > https://gitlab.com/Linaro/lkft/mirrors/stable/linux-stable-rc/-/jobs/3728198425#L1676 > https://storage.tuxsuite.com/public/linaro/lkft/builds/2LPeQeCIu0YEfltwqAFCvDaj29A/ I think we should drop the patch "[PATCH 6.1 012/208] selftests/vm: remove __USE_GNU in hugetlb-madvise.c" from this merge. That patch fixes commit 62f33fa22800 ("selftests/vm: use memfd for hugetlb-madvise test"), but that's only in 6.2-rc1 and it's not in 6.1. I don't really know why it got picked for 6.1 stable backport, because the original patch doesn't contain "CC: stable". Thanks, -- Peter Xu