From: Krzysztof Kozlowski <krzk@kernel.org>
To: Aleksandr Mishin <amishin@t-argos.ru>,
Samuel Ortiz <sameo@linux.intel.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
lvc-project@linuxtesting.org
Subject: Re: [PATCH] nfc: pn533: Add poll mod list filling check
Date: Thu, 4 Jul 2024 14:07:49 +0200 [thread overview]
Message-ID: <ed68c600-aca8-4773-94e3-92347e79877c@kernel.org> (raw)
In-Reply-To: <4899faf4-14cc-4e68-86e5-8745b38e5ab1@t-argos.ru>
On 03/07/2024 09:26, Aleksandr Mishin wrote:
>
>
> On 03.07.2024 8:02, Krzysztof Kozlowski wrote:
>> On 02/07/2024 11:39, Aleksandr Mishin wrote:
>>> In case of im_protocols value is 1 and tm_protocols value is 0 this
>>
>> Which im protocol has value 1 in the mask?
>>
>> The pn533_poll_create_mod_list() handles all possible masks, so your
>> case is just not possible to happen.
>
> Exactly. pn533_poll_create_mod_list() handles all possible specified
> masks. No im protocol has value 1 in the mask. In case of 'im_protocol'
Which cannot happen.
> parameter has value of 1, no mod will be added. So dev->poll_mod_count
> will remain 0.
Which cannot happen.
> I assume 'im_protocol' parameter is "external" to this driver, it comes
> from outside and can contain any value, so driver has to be able to
> protect itself from incorrect values.
Did you read what I wrote? It cannot happen.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-07-04 12:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 9:39 Aleksandr Mishin
2024-07-03 5:02 ` Krzysztof Kozlowski
2024-07-03 7:26 ` Aleksandr Mishin
2024-07-04 12:07 ` Krzysztof Kozlowski [this message]
2024-08-05 8:47 ` [lvc-project] " Fedor Pchelkin
2024-08-27 8:48 ` [PATCH v2] " Aleksandr Mishin
2024-08-29 8:26 ` Paolo Abeni
2024-08-29 8:30 ` Paolo Abeni
2024-08-29 9:06 ` Krzysztof Kozlowski
2024-08-29 9:33 ` Paolo Abeni
2024-08-29 9:34 ` Paolo Abeni
2024-08-29 10:02 ` Krzysztof Kozlowski
2024-08-29 10:21 ` patchwork-bot+netdevbpf
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=ed68c600-aca8-4773-94e3-92347e79877c@kernel.org \
--to=krzk@kernel.org \
--cc=amishin@t-argos.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=netdev@vger.kernel.org \
--cc=sameo@linux.intel.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®