From: Andrew Burgess <aburgess@redhat.com>
To: Pedro Alves <pedro@palves.net>, gdb-patches@sourceware.org
Subject: Re: [PATCH 10/31] Thread options & clone events (Linux GDBserver)
Date: Tue, 06 Jun 2023 15:12:11 +0100 [thread overview]
Message-ID: <87h6rk3cjo.fsf@redhat.com> (raw)
In-Reply-To: <20221212203101.1034916-11-pedro@palves.net>
Pedro Alves <pedro@palves.net> writes:
> This patch teaches the Linux GDBserver backend to report clone events
> to GDB, when GDB has requested them with the GDB_THREAD_OPTION_CLONE
> thread option, via the new QThreadOptions packet.
>
> This shuffles code in linux_process_target::handle_extended_wait
> around to a more logical order when we now have to handle and
> potentially report all of fork/vfork/clone.
>
> Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=19675
> Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=27830
> Change-Id: I3a19bc98801ec31e5c6fdbe1ebe17df855142bb2
> ---
> gdbserver/linux-low.cc | 235 ++++++++++++++++++++++-------------------
> gdbserver/linux-low.h | 2 +
> 2 files changed, 129 insertions(+), 108 deletions(-)
>
> diff --git a/gdbserver/linux-low.cc b/gdbserver/linux-low.cc
> index 6f96e16d6f0..d755cda0e44 100644
> --- a/gdbserver/linux-low.cc
> +++ b/gdbserver/linux-low.cc
> @@ -491,7 +491,6 @@ linux_process_target::handle_extended_wait (lwp_info **orig_event_lwp,
> struct lwp_info *event_lwp = *orig_event_lwp;
> int event = linux_ptrace_get_extended_event (wstat);
> struct thread_info *event_thr = get_lwp_thread (event_lwp);
> - struct lwp_info *new_lwp;
>
> gdb_assert (event_lwp->waitstatus.kind () == TARGET_WAITKIND_IGNORE);
>
> @@ -503,7 +502,6 @@ linux_process_target::handle_extended_wait (lwp_info **orig_event_lwp,
> if ((event == PTRACE_EVENT_FORK) || (event == PTRACE_EVENT_VFORK)
> || (event == PTRACE_EVENT_CLONE))
> {
> - ptid_t ptid;
> unsigned long new_pid;
> int ret, status;
>
> @@ -527,61 +525,65 @@ linux_process_target::handle_extended_wait (lwp_info **orig_event_lwp,
> warning ("wait returned unexpected status 0x%x", status);
> }
>
> - if (event == PTRACE_EVENT_FORK || event == PTRACE_EVENT_VFORK)
> + if (debug_threads)
> {
> - struct process_info *parent_proc;
> - struct process_info *child_proc;
> - struct lwp_info *child_lwp;
> - struct thread_info *child_thr;
> + debug_printf ("HEW: Got %s event from LWP %ld, new child is %ld\n",
> + (event == PTRACE_EVENT_FORK ? "fork"
> + : event == PTRACE_EVENT_VFORK ? "vfork"
> + : event == PTRACE_EVENT_CLONE ? "clone"
> + : "???"),
> + ptid_of (event_thr).lwp (),
> + new_pid);
> + }
> +
> + ptid_t child_ptid = (event != PTRACE_EVENT_CLONE
> + ? ptid_t (new_pid, new_pid)
> + : ptid_t (ptid_of (event_thr).pid (), new_pid));
>
> - ptid = ptid_t (new_pid, new_pid);
> + lwp_info *child_lwp = add_lwp (child_ptid);
> + gdb_assert (child_lwp != NULL);
> + child_lwp->stopped = 1;
> + if (event != PTRACE_EVENT_CLONE)
> + child_lwp->must_set_ptrace_flags = 1;
> + child_lwp->status_pending_p = 0;
>
> - threads_debug_printf ("Got fork event from LWP %ld, "
> - "new child is %d",
> - ptid_of (event_thr).lwp (),
> - ptid.pid ());
> + thread_info *child_thr = get_lwp_thread (child_lwp);
>
> + /* If we're suspending all threads, leave this one suspended
> + too. If the fork/clone parent is stepping over a breakpoint,
> + all other threads have been suspended already. Leave the
> + child suspended too. */
> + if (stopping_threads == STOPPING_AND_SUSPENDING_THREADS
> + || event_lwp->bp_reinsert != 0)
> + {
> + threads_debug_printf ("leaving child suspended");
> + child_lwp->suspended = 1;
> + }
> +
> + if (event_lwp->bp_reinsert != 0
> + && supports_software_single_step ()
> + && event == PTRACE_EVENT_VFORK)
> + {
> + /* If we leave single-step breakpoints there, child will
> + hit it, so uninsert single-step breakpoints from parent
> + (and child). Once vfork child is done, reinsert
> + them back to parent. */
> + uninsert_single_step_breakpoints (event_thr);
> + }
> +
> + if (event != PTRACE_EVENT_CLONE)
> + {
> /* Add the new process to the tables and clone the breakpoint
> lists of the parent. We need to do this even if the new process
> will be detached, since we will need the process object and the
> breakpoints to remove any breakpoints from memory when we
> detach, and the client side will access registers. */
> - child_proc = add_linux_process (new_pid, 0);
> + process_info *child_proc = add_linux_process (new_pid, 0);
> gdb_assert (child_proc != NULL);
> - child_lwp = add_lwp (ptid);
> - gdb_assert (child_lwp != NULL);
> - child_lwp->stopped = 1;
> - child_lwp->must_set_ptrace_flags = 1;
> - child_lwp->status_pending_p = 0;
> - child_thr = get_lwp_thread (child_lwp);
> - child_thr->last_resume_kind = resume_stop;
> - child_thr->last_status.set_stopped (GDB_SIGNAL_0);
> -
> - /* If we're suspending all threads, leave this one suspended
> - too. If the fork/clone parent is stepping over a breakpoint,
> - all other threads have been suspended already. Leave the
> - child suspended too. */
> - if (stopping_threads == STOPPING_AND_SUSPENDING_THREADS
> - || event_lwp->bp_reinsert != 0)
> - {
> - threads_debug_printf ("leaving child suspended");
> - child_lwp->suspended = 1;
> - }
>
> - parent_proc = get_thread_process (event_thr);
> + process_info *parent_proc = get_thread_process (event_thr);
> child_proc->attached = parent_proc->attached;
>
> - if (event_lwp->bp_reinsert != 0
> - && supports_software_single_step ()
> - && event == PTRACE_EVENT_VFORK)
> - {
> - /* If we leave single-step breakpoints there, child will
> - hit it, so uninsert single-step breakpoints from parent
> - (and child). Once vfork child is done, reinsert
> - them back to parent. */
> - uninsert_single_step_breakpoints (event_thr);
> - }
> -
> clone_all_breakpoints (child_thr, event_thr);
>
> target_desc_up tdesc = allocate_target_description ();
> @@ -590,88 +592,97 @@ linux_process_target::handle_extended_wait (lwp_info **orig_event_lwp,
>
> /* Clone arch-specific process data. */
> low_new_fork (parent_proc, child_proc);
> + }
>
> - /* Save fork info in the parent thread. */
> - if (event == PTRACE_EVENT_FORK)
> - event_lwp->waitstatus.set_forked (ptid);
> - else if (event == PTRACE_EVENT_VFORK)
> - event_lwp->waitstatus.set_vforked (ptid);
> -
> + /* Save fork/clone info in the parent thread. */
> + if (event == PTRACE_EVENT_FORK)
> + event_lwp->waitstatus.set_forked (child_ptid);
> + else if (event == PTRACE_EVENT_VFORK)
> + event_lwp->waitstatus.set_vforked (child_ptid);
> + else if (event == PTRACE_EVENT_CLONE
> + && (event_thr->thread_options & GDB_THREAD_OPTION_CLONE) != 0)
> + event_lwp->waitstatus.set_thread_cloned (child_ptid);
> +
> + if (event != PTRACE_EVENT_CLONE
> + || (event_thr->thread_options & GDB_THREAD_OPTION_CLONE) != 0)
> + {
> /* The status_pending field contains bits denoting the
> - extended event, so when the pending event is handled,
> - the handler will look at lwp->waitstatus. */
> + extended event, so when the pending event is handled, the
> + handler will look at lwp->waitstatus. */
> event_lwp->status_pending_p = 1;
> event_lwp->status_pending = wstat;
>
> - /* Link the threads until the parent event is passed on to
> - higher layers. */
> + /* Link the threads until the parent's event is passed on to
> + GDB. */
> event_lwp->fork_relative = child_lwp;
> child_lwp->fork_relative = event_lwp;
> -
> - /* If the parent thread is doing step-over with single-step
> - breakpoints, the list of single-step breakpoints are cloned
> - from the parent's. Remove them from the child process.
> - In case of vfork, we'll reinsert them back once vforked
> - child is done. */
> - if (event_lwp->bp_reinsert != 0
> - && supports_software_single_step ())
> - {
> - /* The child process is forked and stopped, so it is safe
> - to access its memory without stopping all other threads
> - from other processes. */
> - delete_single_step_breakpoints (child_thr);
> -
> - gdb_assert (has_single_step_breakpoints (event_thr));
> - gdb_assert (!has_single_step_breakpoints (child_thr));
> - }
> -
> - /* Report the event. */
> - return 0;
> }
>
> - threads_debug_printf
> - ("Got clone event from LWP %ld, new child is LWP %ld",
> - lwpid_of (event_thr), new_pid);
> -
> - ptid = ptid_t (pid_of (event_thr), new_pid);
> - new_lwp = add_lwp (ptid);
> -
> - /* Either we're going to immediately resume the new thread
> - or leave it stopped. resume_one_lwp is a nop if it
> - thinks the thread is currently running, so set this first
> - before calling resume_one_lwp. */
> - new_lwp->stopped = 1;
> + /* If the parent thread is doing step-over with single-step
> + breakpoints, the list of single-step breakpoints are cloned
> + from the parent's. Remove them from the child process.
> + In case of vfork, we'll reinsert them back once vforked
> + child is done. */
> + if (event_lwp->bp_reinsert != 0
> + && supports_software_single_step ())
> + {
> + /* The child process is forked and stopped, so it is safe
> + to access its memory without stopping all other threads
> + from other processes. */
> + delete_single_step_breakpoints (child_thr);
>
> - /* If we're suspending all threads, leave this one suspended
> - too. If the fork/clone parent is stepping over a breakpoint,
> - all other threads have been suspended already. Leave the
> - child suspended too. */
> - if (stopping_threads == STOPPING_AND_SUSPENDING_THREADS
> - || event_lwp->bp_reinsert != 0)
> - new_lwp->suspended = 1;
> + gdb_assert (has_single_step_breakpoints (event_thr));
> + gdb_assert (!has_single_step_breakpoints (child_thr));
> + }
>
> /* Normally we will get the pending SIGSTOP. But in some cases
> we might get another signal delivered to the group first.
> If we do get another signal, be sure not to lose it. */
> if (WSTOPSIG (status) != SIGSTOP)
> {
> - new_lwp->stop_expected = 1;
> - new_lwp->status_pending_p = 1;
> - new_lwp->status_pending = status;
> + child_lwp->stop_expected = 1;
> + child_lwp->status_pending_p = 1;
> + child_lwp->status_pending = status;
> }
> - else if (cs.report_thread_events)
> + else if (event == PTRACE_EVENT_CLONE && cs.report_thread_events)
> {
> - new_lwp->waitstatus.set_thread_created ();
> - new_lwp->status_pending_p = 1;
> - new_lwp->status_pending = status;
> + child_lwp->waitstatus.set_thread_created ();
> + child_lwp->status_pending_p = 1;
> + child_lwp->status_pending = status;
> }
>
> + if (event == PTRACE_EVENT_CLONE)
> + {
> #ifdef USE_THREAD_DB
> - thread_db_notice_clone (event_thr, ptid);
> + thread_db_notice_clone (event_thr, child_ptid);
> #endif
> + }
>
> - /* Don't report the event. */
> - return 1;
> + if (event == PTRACE_EVENT_CLONE
> + && (event_thr->thread_options & GDB_THREAD_OPTION_CLONE) == 0)
> + {
> + threads_debug_printf
> + ("not reporting clone event from LWP %ld, new child is %ld\n",
> + ptid_of (event_thr).lwp (),
> + new_pid);
> + return 1;
> + }
> +
> + /* Leave the child stopped until GDB processes the parent
> + event. */
> + child_thr->last_resume_kind = resume_stop;
> + child_thr->last_status.set_stopped (GDB_SIGNAL_0);
> +
> + /* Report the event. */
> + threads_debug_printf
> + ("reporting %s event from LWP %ld, new child is %ld\n",
> + (event == PTRACE_EVENT_FORK ? "fork"
> + : event == PTRACE_EVENT_VFORK ? "vfork"
> + : event == PTRACE_EVENT_CLONE ? "clone"
> + : "???"),
> + ptid_of (event_thr).lwp (),
> + new_pid);
> + return 0;
> }
> else if (event == PTRACE_EVENT_VFORK_DONE)
> {
> @@ -3527,7 +3538,8 @@ linux_process_target::wait_1 (ptid_t ptid, target_waitstatus *ourstatus,
>
> /* Break the unreported fork relationship chain. */
> if (event_child->waitstatus.kind () == TARGET_WAITKIND_FORKED
> - || event_child->waitstatus.kind () == TARGET_WAITKIND_VFORKED)
> + || event_child->waitstatus.kind () == TARGET_WAITKIND_VFORKED
> + || event_child->waitstatus.kind () == TARGET_WAITKIND_THREAD_CLONED)
Can we not use:
if (is_new_child_status (event_child->waitstatus.kind ()))
here?
I almost asked here: do we really need to check for THREAD_CLONED here,
given the body of the `if` only changes the `fork_relative` field, which
surely is only related to forks, right?
... but then I dug deeper and spotted that the field also used for clone
events now, so: I wonder if we should rename `fork_relative` to
something better, maybe `fork_clone_relative`, or maybe go generic with
something like `related_lwp`?
It just seemed a little confusing (to me).
But otherwise, this patch looks good.
Reviewed-By: Andrew Burgess <aburgess@redhat.com>
Thanks,
Andrew
> {
> event_child->fork_relative->fork_relative = NULL;
> event_child->fork_relative = NULL;
> @@ -4263,15 +4275,14 @@ linux_set_resume_request (thread_info *thread, thread_resume *resume, size_t n)
> continue;
> }
>
> - /* Don't let wildcard resumes resume fork children that GDB
> - does not yet know are new fork children. */
> + /* Don't let wildcard resumes resume fork/vfork/clone
> + children that GDB does not yet know are new children. */
> if (lwp->fork_relative != NULL)
> {
> struct lwp_info *rel = lwp->fork_relative;
>
> if (rel->status_pending_p
> - && (rel->waitstatus.kind () == TARGET_WAITKIND_FORKED
> - || rel->waitstatus.kind () == TARGET_WAITKIND_VFORKED))
> + && is_new_child_status (rel->waitstatus.kind ()))
> {
> threads_debug_printf
> ("not resuming LWP %ld: has queued stop reply",
> @@ -5894,6 +5905,14 @@ linux_process_target::supports_vfork_events ()
> return true;
> }
>
> +/* Return the set of supported thread options. */
> +
> +gdb_thread_options
> +linux_process_target::supported_thread_options ()
> +{
> + return GDB_THREAD_OPTION_CLONE;
> +}
> +
> /* Check if exec events are supported. */
>
> bool
> diff --git a/gdbserver/linux-low.h b/gdbserver/linux-low.h
> index 1594f063f47..69a34fb96fc 100644
> --- a/gdbserver/linux-low.h
> +++ b/gdbserver/linux-low.h
> @@ -234,6 +234,8 @@ class linux_process_target : public process_stratum_target
>
> bool supports_vfork_events () override;
>
> + gdb_thread_options supported_thread_options () override;
> +
> bool supports_exec_events () override;
>
> void handle_new_gdb_connection () override;
> --
> 2.36.0
next prev parent reply other threads:[~2023-06-06 14:12 UTC|newest]
Thread overview: 100+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 20:30 [PATCH 00/31] Step over thread clone and thread exit Pedro Alves
2022-12-12 20:30 ` [PATCH 01/31] displaced step: pass down target_waitstatus instead of gdb_signal Pedro Alves
2023-02-03 10:44 ` Andrew Burgess
2023-03-10 17:15 ` Pedro Alves
2023-03-16 16:07 ` Andrew Burgess
2023-03-22 21:29 ` Andrew Burgess
2023-03-23 15:15 ` Pedro Alves
2023-03-27 12:40 ` Andrew Burgess
2023-03-27 16:21 ` Pedro Alves
2022-12-12 20:30 ` [PATCH 02/31] linux-nat: introduce pending_status_str Pedro Alves
2023-02-03 12:00 ` Andrew Burgess
2023-03-10 17:15 ` Pedro Alves
2023-03-16 16:19 ` Andrew Burgess
2023-03-27 18:05 ` Pedro Alves
2022-12-12 20:30 ` [PATCH 03/31] gdb/linux: Delete all other LWPs immediately on ptrace exec event Pedro Alves
2023-03-21 14:50 ` Andrew Burgess
2023-04-04 13:57 ` Pedro Alves
2023-04-14 19:29 ` Pedro Alves
2023-05-26 15:04 ` Andrew Burgess
2023-11-13 14:04 ` Pedro Alves
2023-05-26 14:45 ` Andrew Burgess
2022-12-12 20:30 ` [PATCH 04/31] Step over clone syscall w/ breakpoint, TARGET_WAITKIND_THREAD_CLONED Pedro Alves
2023-02-04 15:38 ` Andrew Burgess
2023-03-10 17:16 ` Pedro Alves
2023-03-21 16:06 ` Andrew Burgess
2023-11-13 14:05 ` Pedro Alves
2022-12-12 20:30 ` [PATCH 05/31] Support clone events in the remote protocol Pedro Alves
2023-03-22 15:46 ` Andrew Burgess
2023-11-13 14:05 ` Pedro Alves
2022-12-12 20:30 ` [PATCH 06/31] Avoid duplicate QThreadEvents packets Pedro Alves
2023-05-26 15:53 ` Andrew Burgess
2022-12-12 20:30 ` [PATCH 07/31] enum_flags to_string Pedro Alves
2023-01-30 20:07 ` Simon Marchi
2022-12-12 20:30 ` [PATCH 08/31] Thread options & clone events (core + remote) Pedro Alves
2023-01-31 12:25 ` Lancelot SIX
2023-03-10 19:16 ` Pedro Alves
2023-06-06 13:29 ` Andrew Burgess
2023-11-13 14:07 ` Pedro Alves
2022-12-12 20:30 ` [PATCH 09/31] Thread options & clone events (native Linux) Pedro Alves
2023-06-06 13:43 ` Andrew Burgess
2022-12-12 20:30 ` [PATCH 10/31] Thread options & clone events (Linux GDBserver) Pedro Alves
2023-06-06 14:12 ` Andrew Burgess [this message]
2023-11-13 14:07 ` Pedro Alves
2022-12-12 20:30 ` [PATCH 11/31] gdbserver: Hide and don't detach pending clone children Pedro Alves
2023-06-07 16:10 ` Andrew Burgess
2023-11-13 14:08 ` Pedro Alves
2022-12-12 20:30 ` [PATCH 12/31] Remove gdb/19675 kfails (displaced stepping + clone) Pedro Alves
2023-06-07 17:08 ` Andrew Burgess
2022-12-12 20:30 ` [PATCH 13/31] Add test for stepping over clone syscall Pedro Alves
2023-06-07 17:42 ` Andrew Burgess
2023-11-13 14:09 ` Pedro Alves
2022-12-12 20:30 ` [PATCH 14/31] all-stop/synchronous RSP support thread-exit events Pedro Alves
2023-06-07 17:52 ` Andrew Burgess
2023-11-13 14:11 ` Pedro Alves
2023-12-15 18:15 ` Pedro Alves
2022-12-12 20:30 ` [PATCH 15/31] gdbserver/linux-low.cc: Ignore event_ptid if TARGET_WAITKIND_IGNORE Pedro Alves
2022-12-12 20:30 ` [PATCH 16/31] Move deleting thread on TARGET_WAITKIND_THREAD_EXITED to core Pedro Alves
2023-06-08 12:27 ` Andrew Burgess
2022-12-12 20:30 ` [PATCH 17/31] Introduce GDB_THREAD_OPTION_EXIT thread option, fix step-over-thread-exit Pedro Alves
2023-06-08 13:17 ` Andrew Burgess
2022-12-12 20:30 ` [PATCH 18/31] Implement GDB_THREAD_OPTION_EXIT support for Linux GDBserver Pedro Alves
2023-06-08 14:14 ` Andrew Burgess
2022-12-12 20:30 ` [PATCH 19/31] Implement GDB_THREAD_OPTION_EXIT support for native Linux Pedro Alves
2023-06-08 14:17 ` Andrew Burgess
2022-12-12 20:30 ` [PATCH 20/31] gdb: clear step over information on thread exit (PR gdb/27338) Pedro Alves
2023-06-08 15:29 ` Andrew Burgess
2022-12-12 20:30 ` [PATCH 21/31] stop_all_threads: (re-)enable async before waiting for stops Pedro Alves
2023-06-08 15:49 ` Andrew Burgess
2023-11-13 14:12 ` Pedro Alves
2022-12-12 20:30 ` [PATCH 22/31] gdbserver: Queue no-resumed event after thread exit Pedro Alves
2023-06-08 18:16 ` Andrew Burgess
2023-11-13 14:12 ` Pedro Alves
2022-12-12 20:30 ` [PATCH 23/31] Don't resume new threads if scheduler-locking is in effect Pedro Alves
2023-06-08 18:24 ` Andrew Burgess
2023-11-13 14:12 ` Pedro Alves
2022-12-12 20:30 ` [PATCH 24/31] Report thread exit event for leader if reporting thread exit events Pedro Alves
2023-06-09 13:11 ` Andrew Burgess
2022-12-12 20:30 ` [PATCH 25/31] Ignore failure to read PC when resuming Pedro Alves
2023-06-10 10:33 ` Andrew Burgess
2023-11-13 14:13 ` Pedro Alves
2022-12-12 20:30 ` [PATCH 26/31] gdb/testsuite/lib/my-syscalls.S: Refactor new SYSCALL macro Pedro Alves
2023-06-10 10:33 ` Andrew Burgess
2022-12-12 20:30 ` [PATCH 27/31] Testcases for stepping over thread exit syscall (PR gdb/27338) Pedro Alves
2023-06-12 9:53 ` Andrew Burgess
2022-12-12 20:30 ` [PATCH 28/31] Document remote clone events, and QThreadOptions packet Pedro Alves
2023-06-05 15:53 ` Andrew Burgess
2023-11-13 14:13 ` Pedro Alves
2023-06-12 12:06 ` Andrew Burgess
2023-11-13 14:15 ` Pedro Alves
2022-12-12 20:30 ` [PATCH 29/31] inferior::clear_thread_list always silent Pedro Alves
2023-06-12 12:20 ` Andrew Burgess
2022-12-12 20:31 ` [PATCH 30/31] Centralize "[Thread ...exited]" notifications Pedro Alves
2023-02-04 16:05 ` Andrew Burgess
2023-03-10 17:21 ` Pedro Alves
2023-02-16 15:40 ` Andrew Burgess
2023-06-12 12:23 ` Andrew Burgess
2022-12-12 20:31 ` [PATCH 31/31] Cancel execution command on thread exit, when stepping, nexting, etc Pedro Alves
2023-06-12 13:12 ` Andrew Burgess
2023-01-24 19:47 ` [PATCH v3 00/31] Step over thread clone and thread exit Pedro Alves
2023-11-13 14:24 ` [PATCH " Pedro Alves
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=87h6rk3cjo.fsf@redhat.com \
--to=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@palves.net \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).