From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp-out1.suse.de (smtp-out1.suse.de [195.135.220.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 625ED2F45 for ; Wed, 9 Nov 2022 11:38:52 +0000 (UTC) Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out1.suse.de (Postfix) with ESMTPS id 6E12B21C3A; Wed, 9 Nov 2022 11:38:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_rsa; t=1667993930; h=from:from: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=b3H2YfrTeZRMEuaURCpH7PJ90j0TDo0blJ2eSwkjItQ=; b=s0Pb0P8w6HVcYu5nwIG461XtzjPvtFA9rIaqzg44lro/BxkZEjJtNHy3JfQVBt1o9n3hIJ DBPAwguqKdY9y7LDSm6zV/BsHK0yMu/d6+u2UaTQ9Dtf/1klk2JVN9ABKH+OfeH5Ig8eWr yRGWkYvgjhVLriW8FhfPq6bDZCvozCA= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_ed25519; t=1667993930; h=from:from: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=b3H2YfrTeZRMEuaURCpH7PJ90j0TDo0blJ2eSwkjItQ=; b=Q7WUbqWXu+ksn1DjRBuT4NdOXsqAzjK9K8L0wao9ypgXo90JE42yFgN0H03cis6jagnTFy UStD+Q6ZvT5KARAg== Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id 5A0091331F; Wed, 9 Nov 2022 11:38:50 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id hOPuFUqRa2O7QQAAMHmgww (envelope-from ); Wed, 09 Nov 2022 11:38:50 +0000 Received: by quack3.suse.cz (Postfix, from userid 1000) id E01F4A0704; Wed, 9 Nov 2022 12:38:49 +0100 (CET) Date: Wed, 9 Nov 2022 12:38:49 +0100 From: Jan Kara To: Andrew Morton Cc: Dan Williams , Jason Gunthorpe , Jan Kara , Christoph Hellwig , "Darrick J. Wong" , Matthew Wilcox , John Hubbard , linux-fsdevel@vger.kernel.org, nvdimm@lists.linux.dev, linux-xfs@vger.kernel.org, linux-mm@kvack.org, linux-ext4@vger.kernel.org Subject: Re: [PATCH v2 00/18] Fix the DAX-gup mistake Message-ID: <20221109113849.p7pwob533ijgrytu@quack3> References: <166329930818.2786261.6086109734008025807.stgit@dwillia2-xfh.jf.intel.com> <20221108162059.2ee440d5244657c4f16bdca0@linux-foundation.org> Precedence: bulk X-Mailing-List: nvdimm@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20221108162059.2ee440d5244657c4f16bdca0@linux-foundation.org> On Tue 08-11-22 16:20:59, Andrew Morton wrote: > All seems to be quiet on this front, so I plan to move this series into > mm-stable a few days from now. > > We do have this report of dax_holder_notify_failure being unavailable > with CONFIG_DAX=n: > https://lkml.kernel.org/r/202210230716.tNv8A5mN-lkp@intel.com but that > appears to predate this series. Andrew, there has been v3 some time ago [1] and even that gathered some non-trivial feedback from Jason so I don't think this is settled... [1] https://lore.kernel.org/all/166579181584.2236710.17813547487183983273.stgit@dwillia2-xfh.jf.intel.com Honza -- Jan Kara SUSE Labs, CR