Linux Tegra architecture development
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Jon Hunter <jonathanh@nvidia.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.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,
	f.fainelli@gmail.com, sudipm.mukherjee@gmail.com,
	srw@sladewatkins.net, rwarsow@gmx.de, conor@kernel.org,
	allen.lkml@gmail.com, broonie@kernel.org,
	linux-tegra@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 6.11 000/558] 6.11.3-rc1 review
Date: Wed, 9 Oct 2024 17:57:56 -0400	[thread overview]
Message-ID: <Zwb8ZJlhwz8YxAur@sashalap> (raw)
In-Reply-To: <b222ca24-0d69-4893-b669-02a071e529bf@nvidia.com>

On Wed, Oct 09, 2024 at 04:11:19PM +0100, Jon Hunter wrote:
>Hi Greg,
>
>On 09/10/2024 15:59, Jon Hunter wrote:
>>On Tue, 08 Oct 2024 14:00:30 +0200, Greg Kroah-Hartman wrote:
>>>This is the start of the stable review cycle for the 6.11.3 release.
>>>There are 558 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, 10 Oct 2024 11:55:15 +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.11.3-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.11.y
>>>and the diffstat can be found below.
>>>
>>>thanks,
>>>
>>>greg k-h
>>
>>Failures detected for Tegra ...
>>
>>Test results for stable-v6.11:
>>     10 builds:	10 pass, 0 fail
>>     26 boots:	26 pass, 0 fail
>>     116 tests:	115 pass, 1 fail
>>
>>Linux version:	6.11.3-rc1-gdd3578144a91
>>Boards tested:	tegra124-jetson-tk1, tegra186-p2771-0000,
>>                 tegra194-p2972-0000, tegra194-p3509-0000+p3668-0000,
>>                 tegra20-ventana, tegra210-p2371-2180,
>>                 tegra210-p3450-0000, tegra30-cardhu-a04
>>
>>Test failures:	tegra194-p2972-0000: boot.py
>
>
>The above is a new kernel warning introduced by ...
>
>Michal Koutný <mkoutny@suse.com>
>    cgroup: Disallow mounting v1 hierarchies without controller implementation
>
>
>Interestingly the commit message for the above actually states ...
>
>"Wrap implementation into a helper function, leverage legacy_files to
> detect compiled out controllers. The effect is that mounts on v1 would
> fail and produce a message like:
>   [ 1543.999081] cgroup: Unknown subsys name 'memory'"
>
>The above is the exact warning we see ...
>
>boot: logs: [       8.673272] ERR KERN cgroup: Unknown subsys name 'memory'
>
>
>So although this appears deliberate, I don't see this on mainline/next.

I'll drop it, looks like there are some dependencies needed.

-- 
Thanks,
Sasha

      reply	other threads:[~2024-10-09 21:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241008115702.214071228@linuxfoundation.org>
2024-10-09 14:59 ` [PATCH 6.11 000/558] 6.11.3-rc1 review Jon Hunter
2024-10-09 15:11   ` Jon Hunter
2024-10-09 21:57     ` Sasha Levin [this message]

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=Zwb8ZJlhwz8YxAur@sashalap \
    --to=sashal@kernel.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=gregkh@linuxfoundation.org \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox