public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Daniel Díaz" <daniel.diaz@linaro.org>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
	linux-nfs@vger.kernel.org, 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,
	conor@kernel.org, Olga Kornievskaia <kolga@netapp.com>,
	Benjamin Coddington <bcodding@redhat.com>,
	Anna Schumaker <Anna.Schumaker@netapp.com>,
	Trond Myklebust <trond.myklebust@hammerspace.com>,
	LTP List <ltp@lists.linux.it>, Petr Vorel <pvorel@suse.cz>,
	Richard Palethorpe <rpalethorpe@suse.com>,
	Eryu Guan <eguan@redhat.com>, chrubis <chrubis@suse.cz>
Subject: Re: [PATCH 6.1 000/259] 6.1.56-rc1 review
Date: Sat, 7 Oct 2023 10:58:24 +0200	[thread overview]
Message-ID: <2023100755-livestock-barcode-fe41@gregkh> (raw)
In-Reply-To: <CAEUSe78O-Ho=22nTeioT4eqPRoDNfcWCpc=5O=B59eaMvOkzpg@mail.gmail.com>

On Fri, Oct 06, 2023 at 12:42:04PM -0600, Daniel Díaz wrote:
> Hello!
> 
> On Thu, 5 Oct 2023 at 10:40, Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
> > On Wed, 4 Oct 2023 at 23:41, Greg Kroah-Hartman
> > <gregkh@linuxfoundation.org> wrote:
> > >
> > > This is the start of the stable review cycle for the 6.1.56 release.
> > > There are 259 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 Fri, 06 Oct 2023 17:51:12 +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.56-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.
> > Regressions on arm64 bcm2711-rpi-4-b device running LTP dio tests on
> > NFS mounted rootfs.
> > and LTP hugetlb hugemmap11 test case failed on x86 and arm64 bcm2711-rpi-4-b.
> >
> > Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
> >
> > LTP hugetlb tests failed log
> >   tst_hugepage.c:83: TINFO: 1 hugepage(s) reserved
> >   tst_test.c:1558: TINFO: Timeout per run is 0h 05m 00s
> >   hugemmap11.c:47: TFAIL: Memory mismatch after Direct-IO write
> >
> > LTP dio tests failed log
> >   compare_file: char mismatch: infile offset 4096: 0x01 .   outfile
> > offset 4096: 0x00 .
> >   diotest01    1  TFAIL  :  diotest1.c:158: file compare failed for
> > infile and outfile
> 
> Bisection led to "NFS: Fix O_DIRECT locking issues" (upstream commit
> 7c6339322ce0c6128acbe36aacc1eeb986dd7bf1). Reverting that patch and
> "NFS: Fix error handling for O_DIRECT write scheduling" (upstream
> commit 954998b60caa8f2a3bf3abe490de6f08d283687a) (not a clean revert
> this one) made ltp-dio pass again.

So this is also an issue in Linus's tree?  Or is it only on the 6.1.y
tree.

thanks,

greg k-h

  reply	other threads:[~2023-10-07  8:58 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-04 17:52 [PATCH 6.1 000/259] 6.1.56-rc1 review Greg Kroah-Hartman
2023-10-04 19:33 ` Florian Fainelli
2023-10-04 20:19   ` Namhyung Kim
2023-10-05  0:51     ` Florian Fainelli
2023-10-05  5:15       ` Namhyung Kim
2023-10-06 10:12         ` Greg Kroah-Hartman
2023-10-05  0:17 ` Wang Yugui
2023-10-06 10:12   ` Greg Kroah-Hartman
2023-10-05  0:59 ` Shuah Khan
2023-10-05  1:32 ` SeongJae Park
2023-10-05  3:41 ` Bagas Sanjaya
2023-10-05 12:27 ` Pavel Machek
2023-10-06 12:55   ` Greg Kroah-Hartman
2023-10-05 13:57 ` Takeshi Ogasawara
2023-10-05 16:39 ` Naresh Kamboju
2023-10-05 17:24   ` Petr Vorel
2023-10-05 19:20     ` Naresh Kamboju
2023-10-06  6:41       ` Petr Vorel
2023-10-06 18:42   ` Daniel Díaz
2023-10-07  8:58     ` Greg Kroah-Hartman [this message]
2023-10-09 16:43       ` Naresh Kamboju
2023-10-05 18:40 ` Allen Pais
2023-10-05 22:17 ` Guenter Roeck
2023-10-06  7:30 ` Ron Economos
2023-10-06  9:32 ` Jon Hunter

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=2023100755-livestock-barcode-fe41@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=Anna.Schumaker@netapp.com \
    --cc=akpm@linux-foundation.org \
    --cc=bcodding@redhat.com \
    --cc=chrubis@suse.cz \
    --cc=conor@kernel.org \
    --cc=daniel.diaz@linaro.org \
    --cc=eguan@redhat.com \
    --cc=f.fainelli@gmail.com \
    --cc=jonathanh@nvidia.com \
    --cc=kolga@netapp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lkft-triage@lists.linaro.org \
    --cc=ltp@lists.linux.it \
    --cc=naresh.kamboju@linaro.org \
    --cc=patches@kernelci.org \
    --cc=patches@lists.linux.dev \
    --cc=pavel@denx.de \
    --cc=pvorel@suse.cz \
    --cc=rpalethorpe@suse.com \
    --cc=rwarsow@gmx.de \
    --cc=shuah@kernel.org \
    --cc=srw@sladewatkins.net \
    --cc=stable@vger.kernel.org \
    --cc=sudipm.mukherjee@gmail.com \
    --cc=torvalds@linux-foundation.org \
    --cc=trond.myklebust@hammerspace.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox