Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp897961ybl; Fri, 30 Aug 2019 08:43:00 -0700 (PDT) X-Google-Smtp-Source: APXvYqwi75RxriKnszMEUnnPKYXGD+gasWCJD62YUQN90L8/RTN9Mp+n2qXrJks57GCiZJj6p67b X-Received: by 2002:a62:5214:: with SMTP id g20mr1793904pfb.103.1567179780102; Fri, 30 Aug 2019 08:43:00 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1567179780; cv=none; d=google.com; s=arc-20160816; b=BUBxWveWaBdNkFRcmwZrkKXsX/OUNnOl0f6QmvNghl0Zn+oXq1CWRZ+Y/kyoj+o+I2 ndP6fevAcLLJ1agNocdBaAjzwmJTA6asKusOen1pPBzfgP88rp49tn7vNV+cojwmJGWn V4jH0zgabAvXetE0wavvukO0LQYBBa/HjN2mQ6BTZy0wUVnB7cQOeRVsaBuxoDJ0ES+T WttMeiCJc05CNTghkCpVKEYKh9QMxxTE7KDXHUrEF9tDh4Fph1ZMYWpWH0EzfAYtNifL c3NwKgY33gWNuBbooudw/pV/9+jxuAvpiwgd2quUE5Ix70Ntv/lp4E9KCbG8PjChHFsP OksA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=AwuaoYu0IyfQikEBEJPukjFA7bpLhInpq+H/GaRVWzg=; b=F0m9/RhlXqBw6twfZHRH55rmEhoVWDtilw7yYgXC5EqFE9BkZ2wCuAZ4ivK+t30Jwq emhGVb2yQeHY0w/ndQf1/SDTxzcUhL+HJbPkSqVg9tO4DO9xN/LboiTfEbcFUHuKyeZM UFAZ0SURHnTtq8DKYd993IkAW0bw2IkkmLg0rlY3GgSnlQ2SjD93nmT2YbWW9YteVsGM BZGh1uv7hDdzYL04Mj6KLn4rrHDG+JdTuHB4TsYSmDo/vcJADVBfwB/DsJLypiZX8CZX o/F/+70Vh8kkcS64JVqP2vAHy0nEp9iYlBF+Nu9YYMu7f3tA2kJPsPKwKyeduURdMDyX 7avw== 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 33si4998889plu.194.2019.08.30.08.42.44; Fri, 30 Aug 2019 08:43:00 -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 S1728256AbfH3PkZ (ORCPT + 99 others); Fri, 30 Aug 2019 11:40:25 -0400 Received: from mx2.suse.de ([195.135.220.15]:45286 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727434AbfH3PkZ (ORCPT ); Fri, 30 Aug 2019 11:40:25 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 2D789AEF5; Fri, 30 Aug 2019 15:40:24 +0000 (UTC) Received: by quack2.suse.cz (Postfix, from userid 1000) id B91411E43A8; Fri, 30 Aug 2019 17:40:23 +0200 (CEST) Date: Fri, 30 Aug 2019 17:40:23 +0200 From: Jan Kara To: Tejun Heo Cc: Jens Axboe , linux-block@vger.kernel.org, linux-kernel@vger.kernel.org, Jan Kara Subject: Re: [PATCH block/for-next] writeback: add tracepoints for cgroup foreign writebacks Message-ID: <20190830154023.GC25069@quack2.suse.cz> References: <20190829224701.GX2263813@devbig004.ftw2.facebook.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190829224701.GX2263813@devbig004.ftw2.facebook.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu 29-08-19 15:47:19, Tejun Heo wrote: > cgroup foreign inode handling has quite a bit of heuristics and > internal states which sometimes makes it difficult to understand > what's going on. Add tracepoints to improve visibility. > > Signed-off-by: Tejun Heo ... > +TRACE_EVENT(track_foreign_dirty, > + > + TP_PROTO(struct page *page, struct bdi_writeback *wb), > + > + TP_ARGS(page, wb), > + > + TP_STRUCT__entry( > + __array(char, name, 32) > + __field(u64, bdi_id) > + __field(unsigned long, ino) > + __field(unsigned int, memcg_id) > + __field(unsigned int, cgroup_ino) > + __field(unsigned int, page_cgroup_ino) > + ), > + > + TP_fast_assign( > + strncpy(__entry->name, dev_name(wb->bdi->dev), 32); > + __entry->bdi_id = wb->bdi->id; > + __entry->ino = page->mapping->host->i_ino; > + __entry->memcg_id = wb->memcg_css->id; > + __entry->cgroup_ino = __trace_wb_assign_cgroup(wb); > + __entry->page_cgroup_ino = page->mem_cgroup->css.cgroup->kn->id.ino; > + ), Are the page dereferences above safe? I suppose lock_page_memcg() protects the page->mem_cgroup->css.cgroup->kn->id dereference? But page->mapping does not seem to be protected by page lock? Honza -- Jan Kara SUSE Labs, CR