Hi Markus,
On Mon, Oct 3, 2016 at 3:47 PM, SF Markus Elfring
wrote:
>>> Did you notice the check "IS_ERR(bp_data)" and the corresponding reaction
>>> in this update suggestion?
>>
>> Yes, but bp_data may still be a valid (as in "not an error") value.
>
> Thanks for
Hi Markus,
On Mon, Oct 3, 2016 at 3:47 PM, SF Markus Elfring
wrote:
>>> Did you notice the check "IS_ERR(bp_data)" and the corresponding reaction
>>> in this update suggestion?
>>
>> Yes, but bp_data may still be a valid (as in "not an error") value.
>
> Thanks for your constructive feedback.
>
>> Did you notice the check "IS_ERR(bp_data)" and the corresponding reaction
>> in this update suggestion?
>
> Yes, but bp_data may still be a valid (as in "not an error") value.
Thanks for your constructive feedback.
> Your commit a1708a2eaded836b ("KVM: s390: Improve determination of sizes
>> Did you notice the check "IS_ERR(bp_data)" and the corresponding reaction
>> in this update suggestion?
>
> Yes, but bp_data may still be a valid (as in "not an error") value.
Thanks for your constructive feedback.
> Your commit a1708a2eaded836b ("KVM: s390: Improve determination of sizes
Hi Markus,
On Mon, Oct 3, 2016 at 2:28 PM, SF Markus Elfring
wrote:
>>> - if (!bp_data) {
>>> - ret = -ENOMEM;
>>> - goto error;
>>> - }
>>> -
>>> - if (copy_from_user(bp_data,
>>> -
Hi Markus,
On Mon, Oct 3, 2016 at 2:28 PM, SF Markus Elfring
wrote:
>>> - if (!bp_data) {
>>> - ret = -ENOMEM;
>>> - goto error;
>>> - }
>>> -
>>> - if (copy_from_user(bp_data,
>>> - dbg->arch.hw_bp,
>>> -
>> - if (!bp_data) {
>> - ret = -ENOMEM;
>> - goto error;
>> - }
>> -
>> - if (copy_from_user(bp_data,
>> - dbg->arch.hw_bp,
>> - sizeof(*bp_data) * dbg->arch.nr_hw_bp)) {
>> - ret =
>> - if (!bp_data) {
>> - ret = -ENOMEM;
>> - goto error;
>> - }
>> -
>> - if (copy_from_user(bp_data,
>> - dbg->arch.hw_bp,
>> - sizeof(*bp_data) * dbg->arch.nr_hw_bp)) {
>> - ret =
Hi Markus,
On Wed, Aug 24, 2016 at 8:40 PM, SF Markus Elfring
wrote:
> From: Markus Elfring
> Date: Wed, 24 Aug 2016 20:10:09 +0200
>
> * Reuse existing functionality from memdup_user() instead of keeping
> duplicate source code.
>
Hi Markus,
On Wed, Aug 24, 2016 at 8:40 PM, SF Markus Elfring
wrote:
> From: Markus Elfring
> Date: Wed, 24 Aug 2016 20:10:09 +0200
>
> * Reuse existing functionality from memdup_user() instead of keeping
> duplicate source code.
>
> This issue was detected by using the Coccinelle software.
On Wed, 24 Aug 2016 20:40:03 +0200
SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Wed, 24 Aug 2016 20:10:09 +0200
>
> * Reuse existing functionality from memdup_user() instead of keeping
> duplicate source code.
>
>
On Wed, 24 Aug 2016 20:40:03 +0200
SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Wed, 24 Aug 2016 20:10:09 +0200
>
> * Reuse existing functionality from memdup_user() instead of keeping
> duplicate source code.
>
> This issue was detected by using the Coccinelle software.
>
> *
From: Markus Elfring
Date: Wed, 24 Aug 2016 20:10:09 +0200
* Reuse existing functionality from memdup_user() instead of keeping
duplicate source code.
This issue was detected by using the Coccinelle software.
* Return directly if this copy operation failed.
From: Markus Elfring
Date: Wed, 24 Aug 2016 20:10:09 +0200
* Reuse existing functionality from memdup_user() instead of keeping
duplicate source code.
This issue was detected by using the Coccinelle software.
* Return directly if this copy operation failed.
Reviewed-by: David Hildenbrand
14 matches
Mail list logo