Re: [REGRESSION] 6.6.10+ and 6.7+ kernels lock up early in init.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



[a quick follow up with an important correction from the reporter for
those I added to the list of recipients]

On 23.01.24 06:37, Linux regression tracking (Thorsten Leemhuis) wrote:
> On 23.01.24 05:40, Paul Thompson wrote:
>>
>> 	With my longstanding configuration, kernels upto 6.6.9 work fine.
>> Kernels 6.6.1[0123] and 6.7.[01] all lock up in early (open-rc) init,
>> before even the virtual filesystems are mounted.
>>
>> 	The last thing visible on the console is the nfsclient service
>> being started and:
>>
>> Call to flock failed: Funtion not implemented. (twice)
>>
>> 	Then the machine is unresponsive, numlock doesnt toggle the keyboard led,
>> and the alt-sysrq chords appear to do nothing.
>>
>> 	The problem is solved by changing my 6.6.9 config option:
>>
>> # CONFIG_FILE_LOCKING is not set
>> to
>> CONFIG_FILE_LOCKING=y
>>
>> (This option is under File Systems > Enable POSIX file locking API)

The reporter replied out-of-thread:
https://lore.kernel.org/all/Za9TRtSjubbX0bVu@xxxxxxxxxxxxxxx/

"""
	Now I feel stupid or like Im losing it, but I went back and grepped for
the CONFIG_FILE_LOCKING in my old Configs, and it was turned on in all
but 6.6.9. So, somehow I turned that off *after I built 6.6.9? Argh. I
just built 6.6.4 with it unset and that locked up too.
	Sorry if this is just noise, though one would have hoped the failure
was less severe...
"""

>> 	I do not recall why I unset that, but it was working for I think the
>> entire 6.6 series until 6.6.10. Anyway thought I would mention it in case
>> anyone else hits it.
> 
> Thx for the report.
> 
> CCing a few people to let them known about this. Among them Jeff, who
> had a few fs patches that were backported to 6.6.10 (at the end of
> the list below).
> 
> FWIW, in case anyone wonders what went into that stable release, here
> is a slightly trimmed down list:
> 
> $ git log v6.6.9..v6.6.10 --oneline  | grep -v -e wifi -e ftrace -e kexec -e ksmb -e 'platform/'  -e tracing: -e netfilter: -e mptcp
> c9a51ebb4bac69 Linux 6.6.10
> baa88944038bbe ring-buffer: Fix wake ups when buffer_percent is set to 100
> c62b9a2daf2866 Revert "nvme-fc: fix race between error recovery and creating association"
> d16c5d215b53b3 mm/memory-failure: check the mapcount of the precise page
> 8c7da70d9ae4c1 mm/memory-failure: cast index to loff_t before shifting it
> 07550b1461d4d0 mm: migrate high-order folios in swap cache correctly
> d16eb52c176ccf mm/filemap: avoid buffered read/write race to read inconsistent data
> 09141f08fdf69a selftests: secretmem: floor the memory size to the multiple of page_size
> 2c30b8b105d690 maple_tree: do not preallocate nodes for slot stores
> b5f63f5e8a6820 block: renumber QUEUE_FLAG_HW_WC
> 183c8972b6a6f8 linux/export: Ensure natural alignment of kcrctab array
> 466e9af1550724 linux/export: Fix alignment for 64-bit ksymtab entries
> 28d6cde17f2191 virtio_ring: fix syncs DMA memory with different direction
> 9a49874443307c fs: cifs: Fix atime update check
> 23171df51f601c client: convert to new timestamp accessors
> 5b5599a7eee5e6 fs: new accessor methods for atime and mtime
> 
> Ciao, Thorsten
> 
> 




[Index of Archives]     [Linux Kernel]     [Kernel Development Newbies]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Hiking]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux