From: kensanya <kensanya@163.com>
To: "Leon Romanovsky" <leon@kernel.org>
Cc: bvanassche@acm.org, jgg@ziepe.ca, linux-rdma@vger.kernel.org,
TanZheng <tanzheng@kylinos.cn>
Subject: Re:Re: Re: Re: [PATCH v2] RDMA/srpt: fix NULL deref when sending BUSY before target_init_cmd()
Date: Wed, 29 Jul 2026 12:04:00 +0800 (CST) [thread overview]
Message-ID: <6174be4b.35cc.19fac0b286c.Coremail.kensanya@163.com> (raw)
In-Reply-To: <20260727090046.GJ12003@unreal>
>> There is a contradiction between the two suggestions:
>> - Bart suggests calling target_init_cmd() before calling
>> srpt_get_desc_tbl() (using a placeholder) to ensure that
>> target_send_busy() can be safely executed if the
>> descriptor parsing fails.
>> - Leon points out that target_init_cmd() must receive the
>> actual data direction calculated by srpt_get_desc_tbl(),
>> rather than a placeholder like DMA_NONE that will
>> be overwritten later.
>>
>> If we continue to modify the current patch, the only way I
>> can think of is to extract the direction parsing logic from
>> srpt_get_desc_tbl and place it before target_init_cmd, so
>> that target_init_cmd can receive the correct direction.
>> How about this?
>
>Say it to your AI tool that it is not contradiction, but wrongly
>implemented Bart's suggestion.
>
>Thanks
>
According to my understanding, if we swap the order of srpt_get_desc_tbl
and target_init_cmd and ensure that target_init_cmd can obtain the correct
directory, then my idea is to extract that directory from srpt_get_desc_tbl.
If my understanding or implementation differs from the suggestions you
provided, I have done my best.
Thanks
prev parent reply other threads:[~2026-07-29 4:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 2:44 [PATCH v2] RDMA/srpt: fix NULL deref when sending BUSY before target_init_cmd() kensanya
2026-07-23 9:51 ` Leon Romanovsky
2026-07-24 2:42 ` kensanya
2026-07-26 7:55 ` Leon Romanovsky
2026-07-27 6:39 ` kensanya
2026-07-27 9:00 ` Leon Romanovsky
2026-07-27 17:34 ` Bart Van Assche
2026-07-29 4:04 ` kensanya [this message]
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=6174be4b.35cc.19fac0b286c.Coremail.kensanya@163.com \
--to=kensanya@163.com \
--cc=bvanassche@acm.org \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=tanzheng@kylinos.cn \
/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.