Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp4372631imm; Mon, 6 Aug 2018 23:55:25 -0700 (PDT) X-Google-Smtp-Source: AAOMgpdCSNLM2jXGyfSn0FquOdCvrJpRqf5WkL02HxqHGr37wZHZ/hL0EtMfMlhO2wEG8Mwx+7CD X-Received: by 2002:a63:2906:: with SMTP id p6-v6mr17926907pgp.204.1533624924977; Mon, 06 Aug 2018 23:55:24 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1533624924; cv=none; d=google.com; s=arc-20160816; b=NFtMfaYg/po7+hco7fiYPcmAGqGxpUodGImr/Qv5lhTY/1j0/BJQ7UndM4zQRgMLSj m3qQFS17t+Tb66GrfcUG9taNiiNX9jZ68TV/neq6cugb/c1Y+nBWUkG6fTiMvL6Py6pa Hph1GqsD24E+ZrOOurXDu3jzdMQPqXkYJNy817Kc7mo3SXqbmbNrp0gJbo4EPUivucBs m0dlwCRS8UAWiWRRAGjkF05Z86cpSYxQ4yyHJidt8BjuBkRA2BfXygPiH7ZHe72s1NEk lqUgPwg1BnJ5PaRNThH/tyakI4XhBezvrYn6gE09pUo6lCmKcYIKz/bUYQQjwN0LFrEv Ur3g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date :arc-authentication-results; bh=mE9qSojffEKi34NDUKq/BKGbQNtuV6M8mVzFQWW1iTA=; b=ZGojT09fw1qZmZQ+ipRYteZZMa3d0A0OjiId8qo6Qg0uAoLj8/a5N1JRtwf8h9l8DY U2qQ0CkKUTHbqGK/J6Uz/oSVKto9gG31V4H9oaWMD2rYrsrEvgUurakZdoYAi6lWXspR 22QMSc6Hoh6/zdw59I0v9OQYoP36ZnOTANSvlWArMONEWWWYjNRs6qZU2uJ3kuaDTSuT /lEc83HNwmy9nP26yVIduujAjqAPvIJST6vo3d3PIUb8pmV9Hw8v6f9hAwLth+qn4LXD vrWWxPBvmVVzpvc0bz8AFEfmlWsuKnBxKdpvAkD/+gJ+wc3RnxbWK+K1HG4gJL8XB2BB ivtg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v14-v6si672518pga.270.2018.08.06.23.55.10; Mon, 06 Aug 2018 23:55:24 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388804AbeHGJGz (ORCPT + 99 others); Tue, 7 Aug 2018 05:06:55 -0400 Received: from mx2.suse.de ([195.135.220.15]:58724 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727224AbeHGJGz (ORCPT ); Tue, 7 Aug 2018 05:06:55 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 669F5ADEF; Tue, 7 Aug 2018 06:54:01 +0000 (UTC) Date: Tue, 7 Aug 2018 08:54:00 +0200 From: Johannes Thumshirn To: ard Cc: "Martin K . Petersen" , Linux Kernel Mailinglist , Linux SCSI Mailinglist Subject: Re: [PATCH 0/3] scsi: fcoe: memleak fixes Message-ID: <20180807065400.nxpndw4kf6jdd55i@linux-x5ow.site> References: <20180731134603.20089-1-jthumshirn@suse.de> <20180806092503.6ed56kukj2i236qt@linux-x5ow.site> <20180806132234.GA23827@kwaak.net> <20180806132725.ihbi5rxvkuuppajr@linux-x5ow.site> <20180806142414.GB23827@kwaak.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20180806142414.GB23827@kwaak.net> User-Agent: NeoMutt/20170912 (1.9.0) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Aug 06, 2018 at 04:24:14PM +0200, ard wrote: > I've updated the ticket: > https://github.com/hardkernel/linux/issues/360#issuecomment-410721997 > dmesg (with full debugging): > https://github.com/hardkernel/linux/files/2262858/dmesg-2018-08-06.txt > and kmemleak: > https://github.com/hardkernel/linux/files/2262861/kmemleak-2018-08-06.txt > > I'll have to take a good look at the what and why. > I'm gonna git clean -x -d and rebuild the kernel, because this is > weird. > > This is the tree I build: > https://github.com/ardje/linux/tree/gb-4.14-fcoe-patch > So vanilla linux-4.14 with the patch set: > https://github.com/ardje/linux/commit/747bf04057a99be5b01f768654cfd61bc9f4fc6c > Meh, I should try to use git for patching. > > I will spam some printk's later on, just to check which flows are > followed (if the git clean doesn't reveal some problem, although > I can't imagine). OK, now this is wired. Are you seeing this on the initiator or on the target side? Also on x86_64 or just the odroid? I could reproduce your reports in my Virtualized Environment [1][2] by issuing deletes from the initiator side.. [1] https://github.com/rapido-linux/rapido [2] https://github.com/rapido-linux/rapido/blob/master/fcoe_local_autorun.sh Byte, Johannes -- Johannes Thumshirn Storage jthumshirn@suse.de +49 911 74053 689 SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N?rnberg GF: Felix Imend?rffer, Jane Smithard, Graham Norton HRB 21284 (AG N?rnberg) Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850