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 mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E2914C433F5 for ; Fri, 22 Oct 2021 07:43:26 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 629DD610EA for ; Fri, 22 Oct 2021 07:43:26 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 629DD610EA Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=suse.cz Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=kvack.org Received: by kanga.kvack.org (Postfix) id EE623900003; Fri, 22 Oct 2021 03:43:25 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id E6F03900002; Fri, 22 Oct 2021 03:43:25 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id D0FE7900003; Fri, 22 Oct 2021 03:43:25 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0086.hostedemail.com [216.40.44.86]) by kanga.kvack.org (Postfix) with ESMTP id BC9B6900002 for ; Fri, 22 Oct 2021 03:43:25 -0400 (EDT) Received: from smtpin11.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay04.hostedemail.com (Postfix) with ESMTP id 8097132629 for ; Fri, 22 Oct 2021 07:43:25 +0000 (UTC) X-FDA: 78723283170.11.9436738 Received: from smtp-out1.suse.de (smtp-out1.suse.de [195.135.220.28]) by imf03.hostedemail.com (Postfix) with ESMTP id 2044830000B5 for ; Fri, 22 Oct 2021 07:43:22 +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 DBD3E2197F; Fri, 22 Oct 2021 07:43:22 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_rsa; t=1634888602; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=fYXqzL/6HhifHEzyeb6y/B1mDBHnANb3wM0JqTVeJN4=; b=E1TDhKkVmIVQtRKSIats7Bjc0Q75KzXyErPC+SvzP4SkOnDmhpYEnEJIUXMR+uR3pd+KTL 7N/6y5Ncfn6BH5ECDsGkc/TxCCW1kfcNlP1/TLynAjdEh1drXdjyQR1fswi2xbkIqPiNqT sjGwJjJnnMhvLUeugmD+z6LZo8Rs/cI= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_ed25519; t=1634888602; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=fYXqzL/6HhifHEzyeb6y/B1mDBHnANb3wM0JqTVeJN4=; b=1/OkM3q/XS7FD68wNB6gOmxpXW/2Rn4Xxr3uAgYhCm8tzgQFYSnECUrYNRRnL/FQmzBeHU uwgbaQtnwZgkjBAQ== 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 82E3713C7A; Fri, 22 Oct 2021 07:43:22 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id +PE1H5prcmF7LgAAMHmgww (envelope-from ); Fri, 22 Oct 2021 07:43:22 +0000 Message-ID: <1810283b-164a-800b-63ab-c3fab303a84a@suse.cz> Date: Fri, 22 Oct 2021 09:43:22 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.2.0 Subject: Re: [next] [dragonboard 410c] Unable to handle kernel paging request at virtual address 00000000007c4240 Content-Language: en-US To: Andrew Morton Cc: Jani Nikula , Naresh Kamboju , open list , Linux-Next Mailing List , linux-mm , dri-devel@lists.freedesktop.org, Marco Elver , Vijayanand Jitta , Maarten Lankhorst , Maxime Ripard , Thomas Zimmermann , David Airlie , Daniel Vetter , Andrey Ryabinin , Alexander Potapenko , Andrey Konovalov , Dmitry Vyukov , Geert Uytterhoeven , Oliver Glitta , Imran Khan , lkft-triage@lists.linaro.org, Stephen Rothwell References: <80ab567d-74f3-e14b-3c30-e64bbd64b354@suse.cz> <87fssuojoc.fsf@intel.com> <2a692365-cfa1-64f2-34e0-8aa5674dce5e@suse.cz> <20211021203856.1151daebedef7b180fdfec22@linux-foundation.org> From: Vlastimil Babka In-Reply-To: <20211021203856.1151daebedef7b180fdfec22@linux-foundation.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Stat-Signature: n3aeu88umti3zipmkjuiydj68n6wctcu X-Rspamd-Server: rspam01 X-Rspamd-Queue-Id: 2044830000B5 Authentication-Results: imf03.hostedemail.com; dkim=pass header.d=suse.cz header.s=susede2_rsa header.b=E1TDhKkV; dkim=pass header.d=suse.cz header.s=susede2_ed25519 header.b="1/OkM3q/"; dmarc=none; spf=pass (imf03.hostedemail.com: domain of vbabka@suse.cz designates 195.135.220.28 as permitted sender) smtp.mailfrom=vbabka@suse.cz X-HE-Tag: 1634888602-513310 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 10/22/21 05:38, Andrew Morton wrote: > On Thu, 21 Oct 2021 19:51:20 +0200 Vlastimil Babka wrote: > >> >> Then we have to figure out how to order a fix between DRM and mmotm... >> > >> > That is the question! The problem exists only in the merge of the >> > two. On current DRM side stack_depot_init() exists but it's __init and >> > does not look safe to call multiple times. And obviously my changes >> > don't exist at all in mmotm. >> > >> > I guess one (admittedly hackish) option is to first add a patch in >> > drm-next (or drm-misc-next) that makes it safe to call >> > stack_depot_init() multiple times in non-init context. It would be >> > dropped in favour of your changes once the trees get merged together. >> > >> > Or is there some way for __drm_stack_depot_init() to detect whether it >> > should call stack_depot_init() or not, i.e. whether your changes are >> > there or not? >> >> Let's try the easiest approach first. AFAIK mmotm series is now split to >> pre-next and post-next part > > It has been this way for many years! Aha, great. Looks like I misinterpreted few months ago the thread about adding folio tree to next. >> and moving my patch >> lib-stackdepot-allow-optional-init-and-stack_table-allocation-by-kvmalloc.patch >> with the following fixup to the post-next part should solve this. Would that >> work, Andrew? Thanks. > > For this reason. No probs, thanks. Thanks! > I merge up the post-linux-next parts late in the merge window. I do > need to manually check that the prerequisites are in mainline, because > sometimes the patches apply OK but don't make sense. >