Received: by 2002:a05:6a10:5bc5:0:0:0:0 with SMTP id os5csp2509521pxb; Fri, 29 Oct 2021 02:55:18 -0700 (PDT) X-Google-Smtp-Source: ABdhPJz+jMcbQWkFHStjjlFzmGOD96UaOse1DNTT+iqs4YRMTrLVPOaTpG5IAiCYSQCu4Vhk5LQG X-Received: by 2002:a17:906:c20e:: with SMTP id d14mr12561957ejz.207.1635501318304; Fri, 29 Oct 2021 02:55:18 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1635501318; cv=none; d=google.com; s=arc-20160816; b=Cc0emR+NiOTnzAW8DAtJRE/3m5uFOFcMNouhm+Mxieou3jpQCxmVCWgkf9DCxVfSAE eYJcvwTrhRcFCI3pfdRpNM8Mb17gRff0cYd/gCnBtwvgj+cM5aQW3Zkq2KVQXRc7lLqn 2KmU6GrOHMqzq6m5n9h3YUAtHGmOxSmzWak/JxqnHTv3e2i82RBPNZ6Sth7EHbjVTAGs Q+HJBuZjV01UND8nUJRKgOPZ5tQ/g+Kszq7oKzSrAIr54AG6uh9bLaQ9U0CLtPbv6Jea NGQhtRtGxZiUseYg1cvxC0ZN8BRSK14MNmnpzf2hVcCo9zo0uv3LTGuXIcbaFRc+S5fs edlg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:mail-followup-to:reply-to:message-id :subject:cc:to:from:date:dkim-signature:dkim-signature; bh=zbhf9TEdmvSWX6UxAlSctzmaGQ/0yN4dvgXyDQfs1bc=; b=npym6xMO90Dnn0akrnATw5ME5y9f5HqNPsgXKTPXqugzVSmpfXIFKtFy85oGgGAV6v 3HN94gJTG7vdLk3YopDWCglLOw4AvSLBZ4Ju6QsEeArZMRd2tHh9PP1z970c8H44RZQx dDk+18DJq+8gl9PT+laH5S3gsieyx+xS8P6ChAZWRTWlGjolPOzqZa4GcxGFiez9UJk0 RWrvjsnRTwCBemQWADWnUSB3bJNf3vpPIx6fVizhtCsnndVKlzjClcg20hAwLwBJD9pG MIFe5QguG0kUDg62JChQ+kmvzZb22/ODEtb5AfoLcoLMMAIdGiBZGdELc5G7NjZ/8tK0 qenw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@suse.cz header.s=susede2_rsa header.b=kpX0n4D3; dkim=neutral (no key) header.i=@suse.cz header.s=susede2_ed25519 header.b=1paGujFO; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id c10si7836505ejf.272.2021.10.29.02.54.45; Fri, 29 Oct 2021 02:55:18 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@suse.cz header.s=susede2_rsa header.b=kpX0n4D3; dkim=neutral (no key) header.i=@suse.cz header.s=susede2_ed25519 header.b=1paGujFO; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231602AbhJ2Jz3 (ORCPT + 99 others); Fri, 29 Oct 2021 05:55:29 -0400 Received: from smtp-out2.suse.de ([195.135.220.29]:40970 "EHLO smtp-out2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231534AbhJ2Jz2 (ORCPT ); Fri, 29 Oct 2021 05:55:28 -0400 Received: from relay2.suse.de (relay2.suse.de [149.44.160.134]) by smtp-out2.suse.de (Postfix) with ESMTP id 92B151FD53; Fri, 29 Oct 2021 09:52:59 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_rsa; t=1635501179; h=from:from:reply-to:reply-to:date:date:message-id:message-id:to:to: cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=zbhf9TEdmvSWX6UxAlSctzmaGQ/0yN4dvgXyDQfs1bc=; b=kpX0n4D3WjbuWYFaOkwRRUDXDH5aZjxfHh6ItZifGbh/A4WZ13D7CIPHwtYklAF939dLhT cyRhzXty2BC/XJO8Vui9n4ispAn1pC8dyxmOsNqIpHl0I+mSxThQ5WRzVlbMox+NpwUJIu obc6ZKz1gyk4S/4iAYQIe2M6WqSxv9Y= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_ed25519; t=1635501179; h=from:from:reply-to:reply-to:date:date:message-id:message-id:to:to: cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=zbhf9TEdmvSWX6UxAlSctzmaGQ/0yN4dvgXyDQfs1bc=; b=1paGujFOqQ2Tath2BOt8dXuTEQ7H3A76HKvftk+ZMUCAkevk7xuZUfFn5wDiaEq7uJ/h8E pUZDpXeZBlu5q7Dg== Received: from ds.suse.cz (ds.suse.cz [10.100.12.205]) by relay2.suse.de (Postfix) with ESMTP id 8674AA3B83; Fri, 29 Oct 2021 09:52:59 +0000 (UTC) Received: by ds.suse.cz (Postfix, from userid 10065) id 5A20BDA7A9; Fri, 29 Oct 2021 11:52:26 +0200 (CEST) Date: Fri, 29 Oct 2021 11:52:26 +0200 From: David Sterba To: Stephen Rothwell Cc: Linux Kernel Mailing List , Linux Next Mailing List , Kees Cook , Andrew Morton Subject: Re: linux-next: build failure after merge of the btrfs tree Message-ID: <20211029095226.GV20319@suse.cz> Reply-To: dsterba@suse.cz Mail-Followup-To: dsterba@suse.cz, Stephen Rothwell , Linux Kernel Mailing List , Linux Next Mailing List , Kees Cook , Andrew Morton References: <20211027210924.22ef5881@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20211027210924.22ef5881@canb.auug.org.au> User-Agent: Mutt/1.5.23.1-rc1 (2014-03-12) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Oct 27, 2021 at 09:09:24PM +1100, Stephen Rothwell wrote: > Hi all, > > [I am not sure why this error only popped up after I merged Andrew's > patch set ...] > > After merging the btrfs tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > In file included from include/linux/string.h:253, > from include/linux/bitmap.h:11, > from include/linux/cpumask.h:12, > from arch/x86/include/asm/cpumask.h:5, > from arch/x86/include/asm/msr.h:11, > from arch/x86/include/asm/processor.h:22, > from arch/x86/include/asm/cpufeature.h:5, > from arch/x86/include/asm/thread_info.h:53, > from include/linux/thread_info.h:60, > from arch/x86/include/asm/preempt.h:7, > from include/linux/preempt.h:78, > from include/linux/spinlock.h:55, > from include/linux/wait.h:9, > from include/linux/mempool.h:8, > from include/linux/bio.h:8, > from fs/btrfs/ioctl.c:7: > In function 'memcpy', > inlined from '_btrfs_ioctl_send' at fs/btrfs/ioctl.c:4846:3: > include/linux/fortify-string.h:219:4: error: call to '__write_overflow' declared with attribute error: detected write beyond size of object (1st parameter) > 219 | __write_overflow(); > | ^~~~~~~~~~~~~~~~~~ > > Caused by commit > > c8d9cdfc766d ("btrfs: send: prepare for v2 protocol") > > This changes the "reserved" field of struct btrfs_ioctl_send_args from 4 u64's to 3, but the above memcpy is copying the "reserved" filed from a struct btrfs_ioctl_send_args_32 (4 u64s) into it. I'll fix it in the next update. There are two structures for the ioctl that need to be in sync but I forgot to do that.