From: Viacheslav Dubeyko <Slava.Dubeyko@ibm.com>
To: "max.kellermann@ionos.com" <max.kellermann@ionos.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>,
"idryomov@gmail.com" <idryomov@gmail.com>,
Xiubo Li <xiubli@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Alex Markuze <amarkuze@redhat.com>
Subject: RE: [PATCH] fs/ceph/io: make ceph_start_io_*() killable
Date: Fri, 6 Jun 2025 17:42:02 +0000 [thread overview]
Message-ID: <5d195404b0c997b65633eab4c0326c9c9466bd85.camel@ibm.com> (raw)
In-Reply-To: <CAKPOu+9GHo3_Uf+b_8-p0Hg=gdJJnRE62Go9UZz9WHqR6WF5Lw@mail.gmail.com>
On Fri, 2025-06-06 at 19:34 +0200, Max Kellermann wrote:
> On Fri, Jun 6, 2025 at 7:15 PM Viacheslav Dubeyko <Slava.Dubeyko@ibm.com> wrote:
> > I see the point. Our last discussion has finished with statement that Max
> > doesn't care about this patch set and we don't need to pick it up. If he changed
> > his mind, then I can return to the review of the patch. :) My understanding was
> > that he prefers another person for the review. :) This is why I keep silence.
>
> I do care, always did. I answered your questions, but they were not
> really about my patch but about whether error handling is necessary.
> Well, yes, of course! The whole point of my patch is to add an error
> condition that did not exist before. If locking can fail, of course
> you have to check that and propagate the error to the caller (and
> unlocking after a failed lock of course leads to sorrow). That is so
> trivial, I don't even know where to start to explain this if that
> isn't already obvious enough.
>
> If you keep questioning that, are you really qualified to do a code review?
>
OK. If I am not good enough, then somebody else can do the review. :)
Thanks,
Slava.
next prev parent reply other threads:[~2025-06-06 17:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-06 16:50 Max Kellermann
2024-12-06 17:40 ` Viacheslav Dubeyko
2024-12-06 18:58 ` Max Kellermann
2024-12-06 19:11 ` Viacheslav Dubeyko
2024-12-06 22:48 ` Max Kellermann
2024-12-09 18:59 ` Viacheslav Dubeyko
2025-05-19 10:15 ` Max Kellermann
2025-06-06 17:08 ` Ilya Dryomov
2025-06-06 17:15 ` Viacheslav Dubeyko
2025-06-06 17:34 ` Max Kellermann
2025-06-06 17:42 ` Viacheslav Dubeyko [this message]
2025-06-09 13:13 ` Ilya Dryomov
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=5d195404b0c997b65633eab4c0326c9c9466bd85.camel@ibm.com \
--to=slava.dubeyko@ibm.com \
--cc=amarkuze@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=max.kellermann@ionos.com \
--cc=xiubli@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
all inboxes | Powered by JetHome®