From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Mark Brown <broonie@kernel.org>
Cc: 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, allen.lkml@gmail.com,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH 6.8 000/340] 6.8.10-rc2 review
Date: Thu, 16 May 2024 14:10:58 +0200 [thread overview]
Message-ID: <2024051628-direness-grazing-d4ee@gregkh> (raw)
In-Reply-To: <8221e12b-4def-4faf-84c6-f2fe208a4bf3@sirena.org.uk>
On Wed, May 15, 2024 at 05:37:15PM +0100, Mark Brown wrote:
> On Wed, May 15, 2024 at 10:27:21AM +0200, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 6.8.10 release.
> > There are 340 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.
>
> I'm seeing issues with the ftrace "Test file and directory owership
> changes for eventfs" test on several platforms, including both 32 Arm
> and whatever random x86_64 box Linaro have in their lab. The logs
> aren't terribly helpful since they just log a "not ok", example here:
>
> https://lava.sirena.org.uk/scheduler/job/265221#L3252
>
> Bisects land on "eventfs: Do not differentiate the toplevel events
> directory" as having introduced the issue. Other stables don't seem to
> be affected.
>
> Bisect log (this one from a Raspberry Pi 3 in 32 bit mode):
>
> # bad: [cfe824b75b3d9d13a891ad1c4a2d6fe0eceed1e9] Linux 6.8.10-rc2
> # good: [f3d61438b613b87afb63118bea6fb18c50ba7a6b] Linux 6.8.9
> # good: [428b806127e00d1c39ed72cbae36dbb4598e58dd] usb: dwc3: core: Prevent phy suspend during init
> # good: [a336529a6498c3e7208415b1c2710872aebf04aa] drm/vmwgfx: Fix invalid reads in fence signaled events
> # good: [dcca5ac4f5de7cca371138049a4a5877a6a3af97] hv_netvsc: Don't free decrypted memory
> git bisect start 'cfe824b75b3d9d13a891ad1c4a2d6fe0eceed1e9' 'f3d61438b613b87afb63118bea6fb18c50ba7a6b' '428b806127e00d1c39ed72cbae36dbb4598e58dd' 'a336529a6498c3e7208415b1c2710872aebf04aa' 'dcca5ac4f5de7cca371138049a4a5877a6a3af97'
> # bad: [cfe824b75b3d9d13a891ad1c4a2d6fe0eceed1e9] Linux 6.8.10-rc2
> git bisect bad cfe824b75b3d9d13a891ad1c4a2d6fe0eceed1e9
> # good: [00dfda4fc19df6f2235723e9529efa94cbc122a2] nvme-pci: Add quirk for broken MSIs
> git bisect good 00dfda4fc19df6f2235723e9529efa94cbc122a2
> # bad: [1239a1c5dc96166a0010de49e4769e08bc6d75b3] Bluetooth: qca: fix wcn3991 device address check
> git bisect bad 1239a1c5dc96166a0010de49e4769e08bc6d75b3
> # good: [a2ede3c7da39a8ab359cd23ebba04603e119ac59] ksmbd: do not grant v2 lease if parent lease key and epoch are not set
> git bisect good a2ede3c7da39a8ab359cd23ebba04603e119ac59
> # bad: [21b410a9ae24348d143dbfe3062eae67d52d5a76] eventfs: Do not differentiate the toplevel events directory
> git bisect bad 21b410a9ae24348d143dbfe3062eae67d52d5a76
> # good: [801cdc1467e661f2b151eeb8a25042593a487c78] tracefs: Still use mount point as default permissions for instances
> git bisect good 801cdc1467e661f2b151eeb8a25042593a487c78
> # first bad commit: [21b410a9ae24348d143dbfe3062eae67d52d5a76] eventfs: Do not differentiate the toplevel events directory
Thanks for the bisection, I'll go drop this from 6.8 and 6.6 queues.
Hopefully 6.9 doesn't also have this issue.
greg k-h
next prev parent reply other threads:[~2024-05-16 12:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-15 8:27 [PATCH 6.8 000/340] 6.8.10-rc2 review Greg Kroah-Hartman
2024-05-15 16:37 ` Mark Brown
2024-05-16 12:10 ` Greg Kroah-Hartman [this message]
2024-05-16 12:15 ` Mark Brown
2024-05-15 18:38 ` Florian Fainelli
2024-05-15 18:44 ` Ron Economos
2024-05-15 19:51 ` Allen
2024-05-16 10:56 ` Naresh Kamboju
2024-05-16 12:02 ` Naresh Kamboju
2024-05-16 18:55 ` Steven Rostedt
2024-05-16 12:34 ` Jon Hunter
2024-05-17 3:27 ` Bagas Sanjaya
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=2024051628-direness-grazing-d4ee@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=allen.lkml@gmail.com \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@denx.de \
--cc=rostedt@goodmis.org \
--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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.