[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131129094419.GJ4186@dhcp-16-126.nay.redhat.com>
Date: Fri, 29 Nov 2013 17:44:19 +0800
From: Dave Young <dyoung@...hat.com>
To: Matt Fleming <matt@...sole-pimps.org>
Cc: linux-kernel@...r.kernel.org, linux-efi@...r.kernel.org,
x86@...nel.org, mjg59@...f.ucam.org, hpa@...or.com,
James.Bottomley@...senPartnership.com, vgoyal@...hat.com,
ebiederm@...ssion.com, horms@...ge.net.au,
kexec@...ts.infradead.org, bp@...en8.de, greg@...ah.com,
toshi.kani@...com
Subject: Re: [PATCH v4 10/12] x86: export x86 boot_params to sysfs
On 11/27/13 at 11:20am, Matt Fleming wrote:
> On Tue, 26 Nov, at 01:57:55PM, Dave Young wrote:
> > +Users:
> > + Kexec Mailing List <kexec@...ts.infradead.org>
>
> "Kexec" please.
Will change
>
> > +static ssize_t version_show(struct kobject *kobj,
> > + struct kobj_attribute *attr, char *buf)
>
> This is pretty strange indentation. Usually we prefer to line up the
> arguments like you've done elsewhere in this file.
Ok.
>
> > +{
> > + return sprintf(buf, "0x%04x\n", boot_params.hdr.version);
> > +}
> > +
> > +static struct kobj_attribute boot_params_version_attr = __ATTR_RO(version);
> > +
> > +static ssize_t boot_params_data_read(struct file *fp, struct kobject *kobj,
> > + struct bin_attribute *bin_attr,
> > + char *buf, loff_t off, size_t count)
> > +{
> > + memcpy(buf, (void *)&boot_params + off, count);
> > + return count;
> > +}
>
> Don't we need some checks here to ensure we don't read past the end of
> boot_params?
The size was added below, so I would assume file read will not beyond the
file size:
.size = sizeof(boot_params),
>
> > +static ssize_t type_show(struct kobject *kobj,
> > + struct kobj_attribute *attr, char *buf)
>
> More whacky indentation.
Will fix
>
> > +static int __init create_setup_data_node(struct kobject *parent,
> > + struct kobject **kobjp, int nr)
>
> Funky indentation.
Will fix
Thanks for review
Dave
--
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/
Powered by blists - more mailing lists