From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Dan Carpenter <dan.carpenter@oracle.com>, target-devel@vger.kernel.org
Cc: David Disseldorp <ddiss@suse.de>,
kernel-janitors@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
linux-scsi@vger.kernel.org
Subject: Re: [0/8] target-iSCSI: Adjustments for several function implementations
Date: Fri, 23 Feb 2018 11:50:50 +0000 [thread overview]
Message-ID: <866a1802-0cd8-48fd-e04f-7dc676ab58a6@users.sourceforge.net> (raw)
In-Reply-To: <20180223101715.xv5dscdaeszqxoyk@mwanda>
>> Can a passed null pointer really work in this function?
>>
>> https://elixir.bootlin.com/linux/v4.16-rc2/source/include/crypto/hash.h#L684
>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/include/crypto/hash.h?id\x0f9da844d87796ac31b04e81ee95e155e9043132#n751
>>
>> static inline struct crypto_tfm *crypto_shash_tfm(struct crypto_shash *tfm)
>> {
>> return &tfm->base;
>> }
>
> Yes. It's not a dereference,
Do any processors treat the zero address still special there?
> it's just doing pointer math to get the address.
Can eventually happen anything unexpected?
Can it be nicer to avoid such a software behaviour concern generally
just by adjusting a few jump labels (as I proposed it)?
Regards,
Markus
WARNING: multiple messages have this Message-ID (diff)
From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Dan Carpenter <dan.carpenter@oracle.com>, target-devel@vger.kernel.org
Cc: David Disseldorp <ddiss@suse.de>,
kernel-janitors@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
linux-scsi@vger.kernel.org
Subject: Re: [0/8] target-iSCSI: Adjustments for several function implementations
Date: Fri, 23 Feb 2018 12:50:50 +0100 [thread overview]
Message-ID: <866a1802-0cd8-48fd-e04f-7dc676ab58a6@users.sourceforge.net> (raw)
In-Reply-To: <20180223101715.xv5dscdaeszqxoyk@mwanda>
>> Can a passed null pointer really work in this function?
>>
>> https://elixir.bootlin.com/linux/v4.16-rc2/source/include/crypto/hash.h#L684
>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/include/crypto/hash.h?id=0f9da844d87796ac31b04e81ee95e155e9043132#n751
>>
>> static inline struct crypto_tfm *crypto_shash_tfm(struct crypto_shash *tfm)
>> {
>> return &tfm->base;
>> }
>
> Yes. It's not a dereference,
Do any processors treat the zero address still special there?
> it's just doing pointer math to get the address.
Can eventually happen anything unexpected?
Can it be nicer to avoid such a software behaviour concern generally
just by adjusting a few jump labels (as I proposed it)?
Regards,
Markus
next prev parent reply other threads:[~2018-02-23 11:50 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 21:40 [PATCH 0/8] target-iSCSI: Adjustments for several function implementations SF Markus Elfring
2017-12-12 21:40 ` SF Markus Elfring
2017-12-12 21:42 ` [PATCH 1/8] target/iscsi: Less function calls in chap_server_compute_md5() after error detection SF Markus Elfring
2017-12-12 21:42 ` SF Markus Elfring
2017-12-12 21:43 ` [PATCH 2/8] target/iscsi: Move resetting of seven variables in chap_server_compute_md5() SF Markus Elfring
2017-12-12 21:43 ` SF Markus Elfring
2017-12-12 21:45 ` [PATCH 3/8] target/iscsi: Delete 36 error messages for a failed memory allocation SF Markus Elfring
2017-12-12 21:45 ` SF Markus Elfring
2017-12-12 21:46 ` [PATCH 4/8] target/iscsi: Delete an unnecessary variable initialisation in iscsit_allocate_ooo_cmdsn SF Markus Elfring
2017-12-12 21:46 ` [PATCH 4/8] target/iscsi: Delete an unnecessary variable initialisation in iscsit_allocate_ooo_cmdsn() SF Markus Elfring
2017-12-12 21:47 ` [PATCH 5/8] target/iscsi: Delete an unnecessary variable initialisation in iscsi_copy_param_list() SF Markus Elfring
2017-12-12 21:47 ` SF Markus Elfring
2017-12-12 21:49 ` [PATCH 6/8] target/iscsi: Delete an unnecessary variable initialisation in iscsi_create_default_para SF Markus Elfring
2017-12-12 21:49 ` [PATCH 6/8] target/iscsi: Delete an unnecessary variable initialisation in iscsi_create_default_params() SF Markus Elfring
2017-12-12 21:50 ` [PATCH 7/8] target/iscsi: Delete an unnecessary variable initialisation in iscsi_set_default_param() SF Markus Elfring
2017-12-12 21:50 ` SF Markus Elfring
2017-12-12 21:52 ` [PATCH 8/8] target/iscsi: Improve 16 size determinations SF Markus Elfring
2017-12-12 21:52 ` SF Markus Elfring
2017-12-13 1:16 ` [PATCH 0/8] target-iSCSI: Adjustments for several function implementations David Disseldorp
2018-02-21 16:45 ` SF Markus Elfring
2018-02-21 16:45 ` SF Markus Elfring
2018-02-21 16:45 ` SF Markus Elfring
2018-02-22 13:36 ` David Disseldorp
2018-02-22 13:36 ` David Disseldorp
2018-02-23 8:19 ` [0/8] " SF Markus Elfring
2018-02-23 8:19 ` SF Markus Elfring
2018-02-22 13:56 ` [PATCH 0/8] " Dan Carpenter
2018-02-22 13:56 ` Dan Carpenter
2018-02-23 9:06 ` [0/8] " SF Markus Elfring
2018-02-23 9:06 ` SF Markus Elfring
2018-02-23 10:17 ` Dan Carpenter
2018-02-23 10:17 ` Dan Carpenter
2018-02-23 11:50 ` SF Markus Elfring [this message]
2018-02-23 11:50 ` SF Markus Elfring
2018-02-22 14:19 ` [PATCH 0/8] " David Disseldorp
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=866a1802-0cd8-48fd-e04f-7dc676ab58a6@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=dan.carpenter@oracle.com \
--cc=ddiss@suse.de \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=target-devel@vger.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.