From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Biggers Subject: Re: [Question] Confusion of the meaning for encrypto API's return value Date: Mon, 16 Dec 2019 09:32:17 -0800 Message-ID: <20191216173217.GD139479@gmail.com> References: <7a4edfcb-c140-bf1b-c674-dbb1b30f9b07@huawei.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <7a4edfcb-c140-bf1b-c674-dbb1b30f9b07@huawei.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com Content-Disposition: inline To: Xu Zaibo Cc: forest.zhouchang@huawei.com, dm-devel@redhat.com, linux-crypto@vger.kernel.org, zhangwei375@huawei.com List-Id: dm-devel.ids On Mon, Dec 16, 2019 at 03:18:54PM +0800, Xu Zaibo wrote: > Hi, > > I get a confusion. > > According to my understanding, That 'crypto_skcipher_encrypt(request)' > returns '-EBUSY ' > > means the caller should call this API again with the request. However, as my > knowledge in > > 'dm-crypt', this means the caller need not call this request again, because > 'dm-crypt' thinks > > that the driver of 'crypto_skcipher_encrypt' will send the request again as > it is not busy. > > So, my question is: what's the meaning of > 'crypto_skcipher_encrypt(request)' returning '-EBUSY '? > > > Cheers, > -EBUSY means that the request was put on the backlog. It will still be completed eventually. - Eric