Received: by 10.192.165.148 with SMTP id m20csp2217112imm; Thu, 3 May 2018 12:22:58 -0700 (PDT) X-Google-Smtp-Source: AB8JxZoi+/bBY2AM2oCxf1nz2Fc4MHPHqA5lohzoSNLZlN12yv3HZNWQccYRvFCanAX6dCGXQwcq X-Received: by 2002:a17:902:7008:: with SMTP id y8-v6mr1032248plk.141.1525375378202; Thu, 03 May 2018 12:22:58 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1525375378; cv=none; d=google.com; s=arc-20160816; b=BAJbXggCusaUpArGHZBHDT7r2ekNymUkED97jXXac/pFm9k3WA7x4TZua2NH+QEDO3 R3oQslH7JhOZhEc/NqEx+H45gcFCueqfQGQI4gY/O9NtMXIOdn0K5IGNDlkJijRSCB+B 1qOnsaHBlWJIrwsxRC/Pgu7viQN3LviONlAY/fS42r7y7FXxZE1ECF2M/W5o7kuck5M8 /UnLPTiftAYUJ8AX6HmJyBz/5kgZwTD1K766WI6tyohk+uzIwRhWe+RxMYG9Gz1hQ153 o4S002pj7AZ96zEXzrgY4CZS2/lYh8Q3zwXPn01jkVtpQ8ePk2a0c4jSy2iD7/mmW1HH wvnQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:from:subject:cc:to:message-id:date :arc-authentication-results; bh=sxOxhmvmypNUJAQGK8nlb4p4eylNN5H+NKjXuPqINl8=; b=coenAHWEyUis38znQfPTsv2eqM83GIu77nTeL8UYiayB+dkiV67oeinGf8ey0ZLy2m FZTBnTrpBRv8wqO4JmXUmCUTj+8YG6rfbbgnfiqbZNDRifM8l+eQ7c0Mxoxn8KgIc1Iq wQRaupPKzhQeHAQvxInWMhof+b+FJODI/orC4oJfrjl1ZsXWMPUMfIeNoBh0ChGnDYJC t35bCMG6BNQzF57kBzuV40//mn74KVO8yloBBummh3rP1UffbdXVqo5560FjfOMlqflB IvlOzSm2Dz/two/LsYV4IQ5DyA8r/X2AzcFbp90mkjMKUo4I8KWgbwi7ZQCFVze8BWzu xpdQ== 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 k16-v6si15498618pli.171.2018.05.03.12.22.44; Thu, 03 May 2018 12:22:58 -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 S1751441AbeECTWR (ORCPT + 99 others); Thu, 3 May 2018 15:22:17 -0400 Received: from shards.monkeyblade.net ([184.105.139.130]:51660 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751115AbeECTWP (ORCPT ); Thu, 3 May 2018 15:22:15 -0400 Received: from localhost (67.110.78.66.ptr.us.xo.net [67.110.78.66]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: davem-davemloft) by shards.monkeyblade.net (Postfix) with ESMTPSA id 0AEA813416BAB; Thu, 3 May 2018 12:22:13 -0700 (PDT) Date: Thu, 03 May 2018 15:22:13 -0400 (EDT) Message-Id: <20180503.152213.740988890883315228.davem@davemloft.net> To: syzbot+df0257c92ffd4fcc58cd@syzkaller.appspotmail.com Cc: jon.maloy@ericsson.com, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com, tipc-discussion@lists.sourceforge.net, ying.xue@windriver.com Subject: Re: KMSAN: uninit-value in strcmp From: David Miller In-Reply-To: <00000000000059f907056b519603@google.com> References: <00000000000059f907056b519603@google.com> X-Mailer: Mew version 6.7 on Emacs 25.3 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.12 (shards.monkeyblade.net [149.20.54.216]); Thu, 03 May 2018 12:22:14 -0700 (PDT) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: syzbot Date: Thu, 03 May 2018 11:44:02 -0700 > Call Trace: > __dump_stack lib/dump_stack.c:17 [inline] > dump_stack+0x185/0x1d0 lib/dump_stack.c:53 > kmsan_report+0x142/0x240 mm/kmsan/kmsan.c:1067 > __msan_warning_32+0x6c/0xb0 mm/kmsan/kmsan_instr.c:683 > strcmp+0xf7/0x160 lib/string.c:329 > tipc_nl_node_get_link+0x220/0x6f0 net/tipc/node.c:1881 > genl_family_rcv_msg net/netlink/genetlink.c:599 [inline] Hmmm, TIPC_NL_LINK_GET uses tipc_nl_policy, which has a proper nesting entry for TIPC_NLA_LINK. I wonder how the code goes about validating TIPC_NLA_LINK_NAME in such a case? Does it? This may be the problem.