Bugzilla – Bug 1219321
tail to sysfs files not working with 64K kernel
Last modified: 2024-03-22 12:31:57 UTC
If using 64K kernel and doing tail to sysfs is not working. There is a patch to coreutils that will resolve this issue https://github.com/coreutils/coreutils/commit/73d119f4f Here is an example when doing tail with 64k page /root/coreutils/src # uname -a Linux XXXX 5.14.21-150500.55.28-64kb #1 SMP PREEMPT_DYNAMIC Fri Sep 22 10:04:29 UTC 2023 (c11336f) aarch64 aarch64 aarch64 GNU/Linux /root/coreutils/src # rpm -qa | grep coreutils coreutils-lang-8.32-150400.7.5.noarch coreutils-8.32-150400.7.5.aarch64 /root/coreutils/src # tail /sys/kernel/mm/transparent_hugepage/defrag /root/coreutils/src # tail /sys/kernel/mm/transparent_hugepage/enabled /root/coreutils/src # If build coreutils with the patch /root/coreutils/src # ./tail /sys/kernel/mm/transparent_hugepage/defrag always defer defer+madvise [madvise] never /root/coreutils/src # ./tail /sys/kernel/mm/transparent_hugepage/enabled [always] madvise never
Thanks for the report, I've already backported commit 73d119f4f to SLE15-SP5 coreutils, and submitted it to maintenance. It is currently only pending package maintainer review. If you require a coreutils package PTF you'll need to raise an L3 request, otherwise the fix will be released in the next update.
(In reply to Anthony Iliopoulos from comment #2) > Thanks for the report, I've already backported commit 73d119f4f to SLE15-SP5 > coreutils, and submitted it to maintenance. It is currently only pending > package maintainer review. > > If you require a coreutils package PTF you'll need to raise an L3 request, > otherwise the fix will be released in the next update. Thanks, I am probably ok for the next update. What is the ETA for the next update? Thanks, Carol
(In reply to Carol Soto from comment #3) > (In reply to Anthony Iliopoulos from comment #2) > > Thanks for the report, I've already backported commit 73d119f4f to SLE15-SP5 > > coreutils, and submitted it to maintenance. It is currently only pending > > package maintainer review. > > > > If you require a coreutils package PTF you'll need to raise an L3 request, > > otherwise the fix will be released in the next update. > > > Thanks, I am probably ok for the next update. What is the ETA for the next > update? I cannot say since it is still pending acceptance review, and after that it depends on the QA/maintenance pipeline. I believe that our maintenance can provide an estimate once it gets accepted.
(In reply to Carol Soto from comment #3) > (In reply to Anthony Iliopoulos from comment #2) > > Thanks for the report, I've already backported commit 73d119f4f to SLE15-SP5 > > coreutils, and submitted it to maintenance. It is currently only pending > > package maintainer review. > > > > If you require a coreutils package PTF you'll need to raise an L3 request, > > otherwise the fix will be released in the next update. > > > Thanks, I am probably ok for the next update. What is the ETA for the next > update? The planned release date according to our Maintenance is expected to be at 2024-03-11. I am resolving the ticket as fixed, but if you need it sooner (via PTF) please do reopen this ticket along with a support request, and L3 will take care of it.
(In reply to Anthony Iliopoulos from comment #8) > (In reply to Carol Soto from comment #3) > > (In reply to Anthony Iliopoulos from comment #2) > > > Thanks for the report, I've already backported commit 73d119f4f to SLE15-SP5 > > > coreutils, and submitted it to maintenance. It is currently only pending > > > package maintainer review. > > > > > > If you require a coreutils package PTF you'll need to raise an L3 request, > > > otherwise the fix will be released in the next update. > > > > > > Thanks, I am probably ok for the next update. What is the ETA for the next > > update? > > The planned release date according to our Maintenance is expected to be at > 2024-03-11. > > I am resolving the ticket as fixed, but if you need it sooner (via PTF) > please do reopen this ticket along with a support request, and L3 will take > care of it. Quick question is this fix available?
(In reply to Carol Soto from comment #9) > Quick question is this fix available? I don't see it as released yet. @Olivier can you please comment on this (since I do not have much visibility into the maintenance/release process). Something seems to be delaying the release.
The fix had been pending a QA review for quite some time, which is now done. I have requested the publication, which should be happening within minutes.
(In reply to Olivier Tilloy from comment #11) > The fix had been pending a QA review for quite some time, which is now done. > I have requested the publication, which should be happening within minutes. Yes I see it now. sudo zypper install coreutils .... The following package is going to be upgraded: coreutils 1 package to upgrade. Overall download size: 963.9 KiB. Already cached: 0 B. After the operation, additional 192.5 KiB will be used. Continue? [y/n/v/...? shows all options] (y): y Retrieving: coreutils-8.32-150400.9.3.1.aarch64 (SLE-Module-Basesystem15-SP5-Updates) (1/1), 963.9 KiB Retrieving: coreutils-8.32-150400.9.3.1.aarch64.rpm ........................................................................................................................................................................................................................................................................................................................[done] Checking for file conflicts: ...............................................................................................................................................................................................................................................................................................................................................[done] (1/1) Installing: coreutils-8.32-150400.9.3.1.aarch64 ......................................................................................................................................................................................................................................................................................................................[done] Running post-transaction scripts ...........................................................................................................................................................................................................................................................................................................................................[done] # tail /sys/kernel/mm/transparent_hugepage/defrag always defer defer+madvise [madvise] never # tail /sys/kernel/mm/transparent_hugepage/enabled [always] madvise never # uname -r 5.14.21-150500.55.52-64kb
SUSE-RU-2024:0929-1: An update that has one fix can now be installed. Category: recommended (moderate) Bug References: 1219321 Maintenance Incident: [SUSE:Maintenance:32564](https://smelt.suse.de/incident/32564/) Sources used: openSUSE Leap 15.5 (src): coreutils-testsuite-8.32-150400.9.3.1, coreutils-8.32-150400.9.3.1, coreutils-single-8.32-150400.9.3.1 SUSE Linux Enterprise Micro for Rancher 5.3 (src): coreutils-8.32-150400.9.3.1 SUSE Linux Enterprise Micro 5.3 (src): coreutils-8.32-150400.9.3.1 SUSE Linux Enterprise Micro for Rancher 5.4 (src): coreutils-8.32-150400.9.3.1 SUSE Linux Enterprise Micro 5.4 (src): coreutils-8.32-150400.9.3.1 SUSE Linux Enterprise Micro 5.5 (src): coreutils-8.32-150400.9.3.1 Basesystem Module 15-SP5 (src): coreutils-8.32-150400.9.3.1 openSUSE Leap 15.4 (src): coreutils-testsuite-8.32-150400.9.3.1, coreutils-8.32-150400.9.3.1, coreutils-single-8.32-150400.9.3.1 openSUSE Leap Micro 5.3 (src): coreutils-8.32-150400.9.3.1 openSUSE Leap Micro 5.4 (src): coreutils-8.32-150400.9.3.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination.