Your message dated Thu, 14 Mar 2024 22:53:45 +0100
with message-id <[email protected]>
and subject line Re: Bug#1060217: plocate command blocks waiting io_uring 
operation
has caused the Debian Bug report #1060217,
regarding plocate command blocks waiting io_uring operation
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1060217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060217
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: plocate
Version: 1.1.18-1
Severity: important
Tags: upstream
X-Debbugs-Cc: [email protected]

Dear Maintainer,

I am trying to get plocate to run on an old ARM-based NAS running Debian
bookworm. Building the database with updatedb works fine, but plocate
command itself blocks forever without giving any results back.

I attached gdb to the process, and the source of the problem appears to
be related to the use of io_uring.

Trying to understand what is going on, I ran plocate under strace as
root. Surprisingly, it ran without blocking.

The same behaviour was observed after self-compiling the latest plocate
(v1.1.21), which is why I am also tagging the issue for the upstream.

More details on the observed behaviour of plocate:

   * blocks waiting some io_uring operation when run directly as root/user
   * does not not block when run under strace as root
   * reports an error for not being able to access the database when run
     under strace as user (which sounds like the expected behaviour)

I recompiled the latest plocate with io_uring support disabled in
meson.build, and the program worked fine. Operation may be slower this
way, but at least it works.

-- System Information:
Debian Release: 12.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'stable-debug'), (500, 'stable')
Architecture: armel (armv5tel)

Kernel: Linux 6.1.0-17-marvell (UP)
Locale: LANG=C.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages plocate depends on:
ii  adduser     3.134
ii  libatomic1  12.2.0-14
ii  libc6       2.36-9+deb12u3
ii  libgcc-s1   12.2.0-14
ii  libstdc++6  12.2.0-14
ii  liburing2   2.3-3
ii  libzstd1    1.5.4+dfsg2-5

plocate recommends no packages.

Versions of packages plocate suggests:
ii  powermgmt-base  1.37
ii  systemd-sysv    252.19-1~deb12u1

--- End Message ---
--- Begin Message ---
On Tue, Jan 09, 2024 at 07:39:15PM +0100, Steinar H. Gunderson wrote:
> Can I claim “this is obviously a kernel bug” and pass the buck? :-)

Doing so, since there has been no activity for the last two months.

/* Steinar */
-- 
Homepage: https://www.sesse.net/

--- End Message ---

Reply via email to