From: Atul Kumar Pant <atulpant.linux@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: josef@toxicpanda.com, axboe@kernel.dk,
linux-block@vger.kernel.org, shuah@kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org,
nbd@other.debian.org
Subject: Re: [PATCH v1] drivers: block: Updates return value check
Date: Mon, 7 Aug 2023 17:14:20 +0530 [thread overview]
Message-ID: <20230807114420.GA5826@atom0118> (raw)
In-Reply-To: <2023080600-pretext-corporal-61e3@gregkh>
On Sun, Aug 06, 2023 at 03:36:18PM +0200, Greg KH wrote:
> On Sun, Aug 06, 2023 at 05:53:51PM +0530, Atul Kumar Pant wrote:
> > Updating the check of return value from debugfs_create_dir
> > to use IS_ERR.
>
> Why?
>
> >
> > Signed-off-by: Atul Kumar Pant <atulpant.linux@gmail.com>
> > ---
> > drivers/block/nbd.c | 4 ++--
> > drivers/block/pktcdvd.c | 2 +-
> > 2 files changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/drivers/block/nbd.c b/drivers/block/nbd.c
> > index 9c35c958f2c8..65ecde3e2a5b 100644
> > --- a/drivers/block/nbd.c
> > +++ b/drivers/block/nbd.c
> > @@ -1666,7 +1666,7 @@ static int nbd_dev_dbg_init(struct nbd_device *nbd)
> > return -EIO;
> >
> > dir = debugfs_create_dir(nbd_name(nbd), nbd_dbg_dir);
> > - if (!dir) {
> > + if (IS_ERR(dir)) {
> > dev_err(nbd_to_dev(nbd), "Failed to create debugfs dir for '%s'\n",
> > nbd_name(nbd));
> > return -EIO;
>
> This isn't correct, sorry. Please do not make this change.
>
> > @@ -1692,7 +1692,7 @@ static int nbd_dbg_init(void)
> > struct dentry *dbg_dir;
> >
> > dbg_dir = debugfs_create_dir("nbd", NULL);
> > - if (!dbg_dir)
> > + if (IS_ERR(dbg_dir))
> > return -EIO;
>
> Again, not corrct.
>
> > nbd_dbg_dir = dbg_dir;
> > diff --git a/drivers/block/pktcdvd.c b/drivers/block/pktcdvd.c
> > index d5d7884cedd4..69e5a100b3cf 100644
> > --- a/drivers/block/pktcdvd.c
> > +++ b/drivers/block/pktcdvd.c
> > @@ -451,7 +451,7 @@ static void pkt_debugfs_dev_new(struct pktcdvd_device *pd)
> > if (!pkt_debugfs_root)
> > return;
> > pd->dfs_d_root = debugfs_create_dir(pd->name, pkt_debugfs_root);
> > - if (!pd->dfs_d_root)
> > + if (IS_ERR(pd->dfs_d_root))
> > return;
>
> Also not correct.
>
> Why check the return value at all? As this check has always been wrong,
> why are you wanting to keep it?
I'll check the code again. I was not aware that this check is wrong,
so just tried to fix this based on return value of
debugfs_create_dir.
>
> Also, you never responded to our previous review comments, why not? To
> ignore people is not generally considered a good idea :(
I might have missed seeing your comments hence I did not reply back.
Please accept my sincere apologies for this.
I have one confusion though, regarding the comments that you are
referring to. Are you mentioning about this patch? Re: [PATCH v5] selftests: rtc: Improve rtctest error handling
Here I got the following response from your email bot -
Patch submitter, please ignore Markus's suggestion; you do not need to follow it at all.
Maybe I misunderstood this comment and hence did not reply/do
anything in response to Markus's comments.
If you were referring to some other patch then if possible, can you please tell me the
suject of the patch? I will reply to your comments and will make the
fixes accordingly.
>
> greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Atul Kumar Pant <atulpant.linux@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: axboe@kernel.dk, linux-kernel-mentees@lists.linuxfoundation.org,
josef@toxicpanda.com, nbd@other.debian.org,
linux-block@vger.kernel.org, shuah@kernel.org
Subject: Re: [PATCH v1] drivers: block: Updates return value check
Date: Mon, 7 Aug 2023 17:14:20 +0530 [thread overview]
Message-ID: <20230807114420.GA5826@atom0118> (raw)
In-Reply-To: <2023080600-pretext-corporal-61e3@gregkh>
On Sun, Aug 06, 2023 at 03:36:18PM +0200, Greg KH wrote:
> On Sun, Aug 06, 2023 at 05:53:51PM +0530, Atul Kumar Pant wrote:
> > Updating the check of return value from debugfs_create_dir
> > to use IS_ERR.
>
> Why?
>
> >
> > Signed-off-by: Atul Kumar Pant <atulpant.linux@gmail.com>
> > ---
> > drivers/block/nbd.c | 4 ++--
> > drivers/block/pktcdvd.c | 2 +-
> > 2 files changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/drivers/block/nbd.c b/drivers/block/nbd.c
> > index 9c35c958f2c8..65ecde3e2a5b 100644
> > --- a/drivers/block/nbd.c
> > +++ b/drivers/block/nbd.c
> > @@ -1666,7 +1666,7 @@ static int nbd_dev_dbg_init(struct nbd_device *nbd)
> > return -EIO;
> >
> > dir = debugfs_create_dir(nbd_name(nbd), nbd_dbg_dir);
> > - if (!dir) {
> > + if (IS_ERR(dir)) {
> > dev_err(nbd_to_dev(nbd), "Failed to create debugfs dir for '%s'\n",
> > nbd_name(nbd));
> > return -EIO;
>
> This isn't correct, sorry. Please do not make this change.
>
> > @@ -1692,7 +1692,7 @@ static int nbd_dbg_init(void)
> > struct dentry *dbg_dir;
> >
> > dbg_dir = debugfs_create_dir("nbd", NULL);
> > - if (!dbg_dir)
> > + if (IS_ERR(dbg_dir))
> > return -EIO;
>
> Again, not corrct.
>
> > nbd_dbg_dir = dbg_dir;
> > diff --git a/drivers/block/pktcdvd.c b/drivers/block/pktcdvd.c
> > index d5d7884cedd4..69e5a100b3cf 100644
> > --- a/drivers/block/pktcdvd.c
> > +++ b/drivers/block/pktcdvd.c
> > @@ -451,7 +451,7 @@ static void pkt_debugfs_dev_new(struct pktcdvd_device *pd)
> > if (!pkt_debugfs_root)
> > return;
> > pd->dfs_d_root = debugfs_create_dir(pd->name, pkt_debugfs_root);
> > - if (!pd->dfs_d_root)
> > + if (IS_ERR(pd->dfs_d_root))
> > return;
>
> Also not correct.
>
> Why check the return value at all? As this check has always been wrong,
> why are you wanting to keep it?
I'll check the code again. I was not aware that this check is wrong,
so just tried to fix this based on return value of
debugfs_create_dir.
>
> Also, you never responded to our previous review comments, why not? To
> ignore people is not generally considered a good idea :(
I might have missed seeing your comments hence I did not reply back.
Please accept my sincere apologies for this.
I have one confusion though, regarding the comments that you are
referring to. Are you mentioning about this patch? Re: [PATCH v5] selftests: rtc: Improve rtctest error handling
Here I got the following response from your email bot -
Patch submitter, please ignore Markus's suggestion; you do not need to follow it at all.
Maybe I misunderstood this comment and hence did not reply/do
anything in response to Markus's comments.
If you were referring to some other patch then if possible, can you please tell me the
suject of the patch? I will reply to your comments and will make the
fixes accordingly.
>
> greg k-h
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
next prev parent reply other threads:[~2023-08-07 11:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-06 12:23 [PATCH v1] drivers: block: Updates return value check Atul Kumar Pant
2023-08-06 12:23 ` Atul Kumar Pant
2023-08-06 13:36 ` Greg KH
2023-08-06 13:36 ` Greg KH
2023-08-07 11:44 ` Atul Kumar Pant [this message]
2023-08-07 11:44 ` Atul Kumar Pant
2023-08-08 8:08 ` Greg KH
2023-08-08 8:08 ` Greg KH
2023-08-15 20:32 ` Atul Kumar Pant
2023-08-15 20:32 ` Atul Kumar Pant
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=20230807114420.GA5826@atom0118 \
--to=atulpant.linux@gmail.com \
--cc=axboe@kernel.dk \
--cc=gregkh@linuxfoundation.org \
--cc=josef@toxicpanda.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=nbd@other.debian.org \
--cc=shuah@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.