linux-kernel - Re: [RFC][PATCH v2 10/11] perf: core, lookup pmu via sysfs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20100518201052.GD20223@kroah.com>
Date:	Tue, 18 May 2010 13:10:52 -0700
From:	Greg KH <greg@...ah.com>
To:	Lin Ming <ming.m.lin@...el.com>
Cc:	Peter Zijlstra <peterz@...radead.org>, Ingo Molnar <mingo@...e.hu>,
	Corey Ashford <cjashfor@...ux.vnet.ibm.com>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Paul Mundt <lethal@...ux-sh.org>,
	"eranian@...il.com" <eranian@...il.com>,
	"Gary.Mohr@...l.com" <Gary.Mohr@...l.com>,
	"arjan@...ux.intel.com" <arjan@...ux.intel.com>,
	"Zhang, Yanmin" <yanmin_zhang@...ux.intel.com>,
	Paul Mackerras <paulus@...ba.org>,
	"David S. Miller" <davem@...emloft.net>,
	Russell King <rmk+kernel@....linux.org.uk>,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	Will Deacon <will.deacon@....com>,
	Maynard Johnson <mpjohn@...ibm.com>,
	Carl Love <carll@...ibm.com>,
	Kay Sievers <kay.sievers@...y.org>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: [RFC][PATCH v2 10/11] perf: core, lookup pmu via sysfs

On Wed, May 19, 2010 at 01:49:38AM +0000, Lin Ming wrote:
> Add another pmu lookup method via sysfs.
> Now we have 2 methods: type->pmu and sys_fd->pmu
> 
> Changes log,
> Lookup pmu via sysfs (Ingo Molnar)
> 
> Signed-off-by: Lin Ming <ming.m.lin@...el.com>
> ---
>  kernel/perf_event.c |   33 ++++++++++++++++++++++++++++++++-
>  1 files changed, 32 insertions(+), 1 deletions(-)
> 
> diff --git a/kernel/perf_event.c b/kernel/perf_event.c
> index 8640610..0ab4a8b 100644
> --- a/kernel/perf_event.c
> +++ b/kernel/perf_event.c
> @@ -4680,7 +4680,7 @@ static struct pmu *sw_perf_event_init(struct perf_event *event)
>  	return pmu;
>  }
>  
> -static struct pmu *perf_event_lookup_pmu(struct perf_event *event)
> +static struct pmu *perf_event_lookup_pmu_by_type(struct perf_event *event)
>  {
>  	struct pmu *pmu = NULL;
>  	int pmu_id = PERF_EVENT_ATTR_TYPE(&event->attr);
> @@ -4708,6 +4708,37 @@ static struct pmu *perf_event_lookup_pmu(struct perf_event *event)
>  	return pmu;
>  }
>  
> +static struct pmu *perf_event_lookup_pmu_by_fd(struct perf_event *event)
> +{
> +	struct pmu *pmu = NULL;
> +	struct kobject *kobj;
> +	int sys_fd = PERF_EVENT_ATTR_FD(&event->attr);
> +	struct file *file;
> +	int fput_needed;
> +
> +	file = fget_light(sys_fd, &fput_needed);
> +	if (!file)
> +		return NULL;
> +
> +	kobj = sysfs_get_kobject(file);
> +	if (kobj)
> +		pmu = container_of(kobj, struct pmu, kobj);

Ick, no, I don't think this is a "valid" path to get a kobject.

How would the kernel internally have a file handle, and yet, not have
the kobject?  What is happening that it is so backwards?  Normally the
kobject will get called when its attributes are read or written to, then
you have the kobject handle.  You shouldn't have things the other way
around.

Or am I really missing something here?

> +
> +	fput_light(file, fput_needed);
> +
> +	return pmu;
> +}
> +
> +static struct pmu *perf_event_lookup_pmu(struct perf_event *event)
> +{
> +	u32 type = event->attr.type;
> +
> +	if (type & PERF_EVENT_FD)
> +		return perf_event_lookup_pmu_by_fd(event);

How are we getting here?

totally confused,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/