From: Bert Karwatzki <spasswolf@web•de>
To: Joel Granados <joel.granados@kernel•org>
Cc: linux-kernel@vger•kernel.org, linux-next@vger•kernel.org,
Waiman Long <longman@redhat•com>, Kees Cook <kees@kernel•org>
Subject: Re: register_syctl_init error in linux-next-20250612
Date: Fri, 20 Jun 2025 11:37:40 +0200 [thread overview]
Message-ID: <3eec91e437e2b9861e069a6c63e80b2bfd7e9802.camel@web.de> (raw)
In-Reply-To: <mve232hzw4tqc5rnqlacofzlygqks7uirkumfmibrnmzcmpywh@kpchyerpb4ju>
Am Donnerstag, dem 19.06.2025 um 14:39 +0200 schrieb Joel Granados:
> On Thu, Jun 12, 2025 at 07:55:13PM +0200, Bert Karwatzki wrote:
> > When starting evolution (gnome email client) on my debian sid with
> > linux-next-20250612 I get the following error message on the terminal
> > emulator (the Gtk messages also occur when):
> >
> > Gtk-Message: 13:34:49.069: Failed to load module "colorreload-gtk-module"
> > Gtk-Message: 13:34:49.070: Failed to load module "window-decorations-gtk-module"
> > Gtk-Message: 13:34:51.012: Failed to load module "colorreload-gtk-module"
> > Gtk-Message: 13:34:51.013: Failed to load module "window-decorations-gtk-module"
> > bwrap: Can't read /proc/sys/kernel/overflowuid: No such file or directory
> >
> > ** (org.gnome.Evolution:3327): ERROR **: 13:34:51.245: Failed to fully launch dbus-proxy: Der Kindprozess wurde mit Status 1 beendet
> > Trace/Breakpoint ausgelöst
> >
> > and the following message in dmesg:
> >
> > [ 305.600587] [ T3327] traps: evolution[3327] trap int3 ip:7f64442d3ab7 sp:7ffc9f4e94d0 error:0 in libglib-2.0.so.0.8400.2[66ab7,7f644428c000+a1000]
> >
> > I bisected this to commit cf47285025e6 ("locking/rtmutex: Move max_lock_depth
> > into rtmutex.c"). The absence of /proc/sys/kernel/overflow{uid,gid} seems to be the related
> > to the start failure, in affected kernel version the files are absent while they're present
> > when evolution starts normally.
> I just tested with next-20250619 and I see /proc/sys/kernel/overflow{uid,gid}
>
> >
> > Also when booting next-20250612 I get this error message regarding max_lock_depth and
> > rtmutex_sysctl_table:
> >
> > [ 0.234399] [ T1] sysctl duplicate entry: /kernel/max_lock_depth
> > [ 0.234402] [ T1] failed when register_sysctl_sz rtmutex_sysctl_table to kernel
> > [ 0.234405] [ T1] sysctl duplicate entry: /kernel/max_lock_depth
> > [ 0.234407] [ T1] failed when register_sysctl_sz rtmutex_sysctl_table to kernel
> And I do not see these messages in my dmesg. And
> /proc/sys/kernel/max_lock_depth exists.
>
> Maybe its something that only happened with the version from the 12th?
> Could you test again with the version from the 19?
>
> Best
I tested next-202506{12,17,19} and sysctl-next and they all show the buggy behaviour.
CONFIG_PREEMPT_RT=y is needed for the bug to appear.
Bert Karwatzki
next prev parent reply other threads:[~2025-06-20 9:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-12 17:55 register_syctl_init error in linux-next-20250612 Bert Karwatzki
2025-06-19 11:50 ` Joel Granados
2025-06-19 12:39 ` Joel Granados
2025-06-20 9:37 ` Bert Karwatzki [this message]
2025-06-20 11:11 ` Joel Granados
2025-06-20 11:17 ` Bert Karwatzki
2025-06-23 7:55 ` Joel Granados
-- strict thread matches above, loose matches on Subject: below --
2025-06-19 15:22 Bert Karwatzki
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=3eec91e437e2b9861e069a6c63e80b2bfd7e9802.camel@web.de \
--to=spasswolf@web$(echo .)de \
--cc=joel.granados@kernel$(echo .)org \
--cc=kees@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=longman@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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