From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6444FC433EF for ; Sat, 7 May 2022 21:59:42 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id BE45A6B0073; Sat, 7 May 2022 17:59:41 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id B6CE66B0074; Sat, 7 May 2022 17:59:41 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 9E7286B0075; Sat, 7 May 2022 17:59:41 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0012.hostedemail.com [216.40.44.12]) by kanga.kvack.org (Postfix) with ESMTP id 8C80F6B0073 for ; Sat, 7 May 2022 17:59:41 -0400 (EDT) Received: from smtpin08.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay06.hostedemail.com (Postfix) with ESMTP id 62AE72F067 for ; Sat, 7 May 2022 21:59:41 +0000 (UTC) X-FDA: 79440314562.08.7144F92 Received: from ams.source.kernel.org (ams.source.kernel.org [145.40.68.75]) by imf23.hostedemail.com (Postfix) with ESMTP id 518D114004C for ; Sat, 7 May 2022 21:59:29 +0000 (UTC) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id 9F060B8085B; Sat, 7 May 2022 21:59:39 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 06DFDC385A6; Sat, 7 May 2022 21:59:37 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linux-foundation.org; s=korg; t=1651960778; bh=Ka1X3YltXKyKrA5wqKviT4NwESbjBhPlX4Lz/VQyqIE=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=Nrb95ZZQ19DPLKrY9f0/KQYOZkAtoYQi6gbHeTccHTKEWS0z5hMvyIkyaPC8/aINW Ix7m0nunPoxUi32N87IKhjPLRHRtrcr4ydjgQM3/iofEAAAvXw+AGrrWoJRbktlfM3 gWEVaeesPGd+zf2P6C0gA2fZ0M90TdndEfgJcrxY= Date: Sat, 7 May 2022 14:59:37 -0700 From: Andrew Morton To: "lipeifeng@oppo.com" Cc: michel , hughd , linux-mm , linux-kernel , "Barry Song" <21cnbao@gmail.com>, zhangshiming , peifengl55 Subject: Re: [PATCH] mm: fix align-error when get_addr in unmapped_area_topdown Message-Id: <20220507145937.6dbfc036f99addf9342bc5ce@linux-foundation.org> In-Reply-To: <2022050211305415626916@oppo.com> References: <20220412081014.399-1-lipeifeng@oppo.com> <20220412142238.93e36cc4095e4e0b362db348@linux-foundation.org> <2022041310411426044561@oppo.com> <2022050110235766139218@oppo.com> <20220501181041.6d53cb9ed54bf697840e36cc@linux-foundation.org> <2022050211305415626916@oppo.com> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; x86_64-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Rspamd-Server: rspam02 X-Rspamd-Queue-Id: 518D114004C X-Stat-Signature: a9mx7j1gieygxkb4eh3dih9byt9tz1kf X-Rspam-User: Authentication-Results: imf23.hostedemail.com; dkim=pass header.d=linux-foundation.org header.s=korg header.b=Nrb95ZZQ; spf=pass (imf23.hostedemail.com: domain of akpm@linux-foundation.org designates 145.40.68.75 as permitted sender) smtp.mailfrom=akpm@linux-foundation.org; dmarc=none X-HE-Tag: 1651960769-1253 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Mon, 2 May 2022 11:33:18 +0800 "lipeifeng@oppo.com" wrote: > Hi Andrew： > > Thanks for your quick response. > > > They caused me some merge issues against mapletree, which I had > > resolved.  Mapletree is dropped at present so I set these patches aside > > until the next version of the mapletree patches are available. > > Do we have a definite time for the next available version of the mapletree patches? I merged v2 a couple of days ago. It should be in mm-unstable then linux-next early next week. > Excuse me, is it possible for our patch to be independent of mapletree and brought in separately? Well, the changelog was rather unclear on the real-world end-user visible effects of the defect. When these prioritization decisions are to be made, it really helps to have a clear view of the impact to our users. > > > I've been holding your patches until Michel Lespinasse has had time to > > review them (and hopefully explain them to me ;)).  Please review > > earlier comments which Michel has provided and ensure that those > > comments have been fully addressed so we can hopefully move forward on > > this. > > We will reply soon if Mr.Lespinasse provideds any advices or question. > And I haven't received any reply from Mr.Lespinasse yet, pls let me know > if i missed the reply. There was a big conference last week.