Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752319AbbKTFOU (ORCPT ); Fri, 20 Nov 2015 00:14:20 -0500 Received: from mail-oi0-f43.google.com ([209.85.218.43]:36235 "EHLO mail-oi0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751049AbbKTFOT (ORCPT ); Fri, 20 Nov 2015 00:14:19 -0500 MIME-Version: 1.0 Date: Fri, 20 Nov 2015 13:14:18 +0800 Message-ID: Subject: rhashtable: how to deal with that rhashtable_lookup_insert_key return -EBUSY From: Xin Long To: linux-kernel@vger.kernel.org, network dev Cc: tgraf@suug.ch, herbert@gondor.apana.org.au, davem Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 634 Lines: 15 when I use rhashtable_lookup_insert_key, sometimes it will return -EBUSY. im not sure if there is a good way to workabout it. or I should just try again and again until it's inserted successfully ? I have seen some use in kernel by now, but it seems that no one consider this issue for their cases. but it indeed exists in my case. did I use it incorrectly or something else ? Thanks. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/