From: Andreas Gruenbacher <agruenba@redhat.com>
To: Alexander Aring <aahringo@redhat.com>
Cc: rpeterso@redhat.com, gfs2@lists.linux.dev
Subject: Re: [PATCH] gfs2: don't withdraw if init_threads() got interrupted
Date: Thu, 2 Nov 2023 20:58:00 +0100 [thread overview]
Message-ID: <CAHc6FU4kzYQCmtX+hDBNwufvgZio-zxhO5kGtxJjWfWJMjNZjA@mail.gmail.com> (raw)
In-Reply-To: <20231031143328.1364741-1-aahringo@redhat.com>
Alex,
On Tue, Oct 31, 2023 at 3:33 PM Alexander Aring <aahringo@redhat.com> wrote:
> This patch just don't call gfs2_withdraw_delayed() if init_threads()
> returns -EINTR.
that's close, but calling gfs2_withdraw_delayed() actually never makes
sense in this context. I'll follow up with a patch that describes why.
Thanks,
Andreas
next prev parent reply other threads:[~2023-11-02 19:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 14:33 [PATCH] gfs2: don't withdraw if init_threads() got interrupted Alexander Aring
2023-11-02 19:58 ` Andreas Gruenbacher [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-02 19:58 Andreas Gruenbacher
2023-11-02 20:50 ` Alexander Aring
2023-11-02 22:08 ` Andreas Gruenbacher
2023-11-02 22:11 ` Alexander Aring
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=CAHc6FU4kzYQCmtX+hDBNwufvgZio-zxhO5kGtxJjWfWJMjNZjA@mail.gmail.com \
--to=agruenba@redhat.com \
--cc=aahringo@redhat.com \
--cc=gfs2@lists.linux.dev \
--cc=rpeterso@redhat.com \
/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).