Re: [PATCH] target/core: Avoid that a kernel oops can be triggered when an XCOPY command fails

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Bart Van Assche <bvanassche@xxxxxxx>
Subject: Re: [PATCH] target/core: Avoid that a kernel oops can be triggered when an XCOPY command fails
From: David Disseldorp <ddiss@xxxxxxx>
Date: Tue, 6 Nov 2018 00:19:30 +0100
Cc: "Martin K . Petersen" <martin.petersen@xxxxxxxxxx>, Christoph Hellwig <hch@xxxxxx>, target-devel@xxxxxxxxxxxxxxx, Nicholas Bellinger <nab@xxxxxxxxxxxxxxx>, Mike Christie <mchristi@xxxxxxxxxx>, Hannes Reinecke <hare@xxxxxxx>
In-reply-to: <20181105184011.94041-1-bvanassche@acm.org>
References: <20181105184011.94041-1-bvanassche@acm.org>

On Mon,  5 Nov 2018 10:40:11 -0800, Bart Van Assche wrote:

> Avoid that a kernel oops can be triggered when an XCOPY command fails

FWIW, that should be COMPARE_AND_WRITE instead of XCOPY.

Cheers, David

References:
- [PATCH] target/core: Avoid that a kernel oops can be triggered when an XCOPY command fails
  - From: Bart Van Assche

Prev by Date: Re: [PATCH] target/core: Make it safe to pass NULL as third argument to compare_and_write_callback()
Next by Date: [PATCH v3] target/core: Avoid that a kernel oops is triggered when COMPARE AND WRITE fails
Previous by thread: Re: [PATCH] target/core: Avoid that a kernel oops can be triggered when an XCOPY command fails
Next by thread: [PATCH v3] target/core: Avoid that a kernel oops is triggered when COMPARE AND WRITE fails
Index(es):
- Date
- Thread

[Index of Archives] [Linux SCSI] [Kernel Newbies] [Linux SCSI Target Infrastructure] [Share Photos] [IDE] [Security] [Git] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Linux ATA RAID] [Linux IIO] [Device Mapper]

Powered by Linux