From: Xiubo Li <xiubli@redhat.com>
To: Ilya Dryomov <idryomov@gmail.com>
Cc: Jeff Layton <jlayton@kernel.org>,
Patrick Donnelly <pdonnell@redhat.com>,
Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: [PATCH 1/5] ceph: export ceph_create_session_msg
Date: Thu, 1 Jul 2021 09:50:21 +0800 [thread overview]
Message-ID: <e558085c-d0a8-3ea5-2e66-1a7fe02a2446@redhat.com> (raw)
In-Reply-To: <CAOi1vP-+K1OVA5_Fq6pdC1z0Pp4jLfGB_P+AOzJO9i7oL2uvcg@mail.gmail.com>
On 6/30/21 8:17 PM, Ilya Dryomov wrote:
> On Tue, Jun 29, 2021 at 3:27 PM Xiubo Li <xiubli@redhat.com> wrote:
>>
>> On 6/29/21 9:12 PM, Jeff Layton wrote:
>>> On Tue, 2021-06-29 at 12:42 +0800, xiubli@redhat.com wrote:
>>>> From: Xiubo Li <xiubli@redhat.com>
>>>>
>>> nit: the subject of this patch is not quite right. You aren't exporting
>>> it here, just making it a global symbol (within ceph.ko).
>>>
>> Yeah, will fix it.
>>
>>
>>>> Signed-off-by: Xiubo Li <xiubli@redhat.com>
>>>> ---
>>>> fs/ceph/mds_client.c | 15 ++++++++-------
>>>> fs/ceph/mds_client.h | 1 +
>>>> 2 files changed, 9 insertions(+), 7 deletions(-)
>>>>
>>>> diff --git a/fs/ceph/mds_client.c b/fs/ceph/mds_client.c
>>>> index 2d7dcd295bb9..e49d3e230712 100644
>>>> --- a/fs/ceph/mds_client.c
>>>> +++ b/fs/ceph/mds_client.c
>>>> @@ -1150,7 +1150,7 @@ static int __choose_mds(struct ceph_mds_client *mdsc,
>>>> /*
>>>> * session messages
>>>> */
>>>> -static struct ceph_msg *create_session_msg(u32 op, u64 seq)
>>>> +struct ceph_msg *ceph_create_session_msg(u32 op, u64 seq)
>>>> {
>>>> struct ceph_msg *msg;
>>>> struct ceph_mds_session_head *h;
>>>> @@ -1158,7 +1158,7 @@ static struct ceph_msg *create_session_msg(u32 op, u64 seq)
>>>> msg = ceph_msg_new(CEPH_MSG_CLIENT_SESSION, sizeof(*h), GFP_NOFS,
>>>> false);
>>>> if (!msg) {
>>>> - pr_err("create_session_msg ENOMEM creating msg\n");
>>>> + pr_err("ceph_create_session_msg ENOMEM creating msg\n");
>>> instead of hardcoding the function names in these error messages, use
>>> __func__ instead? That makes it easier to keep up with code changes.
>>>
>>> pr_err("%s ENOMEM creating msg\n", __func__);
>> Sure, will fix this too.
> I think this can be just "ENOMEM creating session msg" without the
> function name to avoid repetition.
Will fix it by using:
pr_err("ENOMEM creating session %s msg", ceph_session_op_name(op));
Thanks.
>
> Thanks,
>
> Ilya
>
next prev parent reply other threads:[~2021-07-01 1:50 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 4:42 [PATCH 0/5] flush the mdlog before waiting on unsafe reqs xiubli
2021-06-29 4:42 ` [PATCH 1/5] ceph: export ceph_create_session_msg xiubli
2021-06-29 13:12 ` Jeff Layton
2021-06-29 13:27 ` Xiubo Li
2021-06-30 12:17 ` Ilya Dryomov
2021-07-01 1:50 ` Xiubo Li [this message]
2021-06-29 4:42 ` [PATCH 2/5] ceph: export iterate_sessions xiubli
2021-06-29 15:39 ` Jeff Layton
2021-06-30 0:55 ` Xiubo Li
2021-06-29 4:42 ` [PATCH 3/5] ceph: flush mdlog before umounting xiubli
2021-06-29 15:34 ` Jeff Layton
2021-06-30 0:36 ` Xiubo Li
2021-06-30 12:39 ` Ilya Dryomov
2021-07-01 1:18 ` Xiubo Li
2021-06-29 4:42 ` [PATCH 4/5] ceph: flush the mdlog before waiting on unsafe reqs xiubli
2021-06-29 13:25 ` Jeff Layton
2021-06-30 1:26 ` Xiubo Li
2021-06-30 12:13 ` Jeff Layton
2021-07-01 1:16 ` Xiubo Li
2021-07-01 3:27 ` Patrick Donnelly
[not found] ` <e917a3e1-2902-604b-5154-98086c95357f@redhat.com>
2021-07-01 23:46 ` Patrick Donnelly
2021-07-02 0:01 ` Xiubo Li
2021-07-02 13:17 ` Xiubo Li
2021-07-02 18:14 ` Patrick Donnelly
2021-07-03 1:33 ` Xiubo Li
2021-06-29 4:42 ` [PATCH 5/5] ceph: fix ceph feature bits xiubli
2021-06-29 15:38 ` Jeff Layton
2021-06-30 0:52 ` Xiubo Li
2021-06-30 12:05 ` Jeff Layton
2021-06-30 12:52 ` Ilya Dryomov
2021-07-01 1:07 ` Xiubo Li
2021-07-01 1:08 ` Xiubo Li
2021-07-01 3:35 ` Xiubo Li
2021-06-29 15:27 ` [PATCH 0/5] flush the mdlog before waiting on unsafe reqs Jeff Layton
2021-06-30 0:35 ` Xiubo Li
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=e558085c-d0a8-3ea5-2e66-1a7fe02a2446@redhat.com \
--to=xiubli@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=jlayton@kernel.org \
--cc=pdonnell@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 NNTP newsgroup(s).