From: Joe Perches <joe@perches.com>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: "Arvind R." <arvino55@gmail.com>, Michal Marek <mmarek@suse.cz>,
linuxppc-dev@lists.ozlabs.org, Mark Gross <mark.gross@intel.com>,
Shaohui Xie <Shaohui.Xie@freescale.com>,
Jason Uhlenkott <juhlenko@akamai.com>,
Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>,
Jiri Kosina <jkosina@suse.cz>,
Ranganathan Desikan <ravi@jetztechnologies.com>,
Borislav Petkov <borislav.petkov@amd.com>,
Chris Metcalf <cmetcalf@tilera.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Egor Martovetsky <egor@pasemi.com>,
Aristeu Rozanski <arozansk@redhat.com>,
Olof Johansson <olof@lixom.net>, Doug Thompson <norsk5@yahoo.com>,
Andrew Morton <akpm@linux-foundation.org>,
Tim Small <tim@buttersideup.com>,
Hitoshi Mitake <h.mitake@gmail.com>,
Linux Edac Mailing List <linux-edac@vger.kernel.org>
Subject: Re: [EDAC ABI v13 24/25] edac: change the mem allocation scheme to make Documentation/kobject.txt happy
Date: Tue, 17 Apr 2012 15:17:47 -0600 [thread overview]
Message-ID: <1334697467.3920.5.camel@joe2Laptop> (raw)
In-Reply-To: <1334608729-30803-25-git-send-email-mchehab@redhat.com>
On Mon, 2012-04-16 at 17:38 -0300, Mauro Carvalho Chehab wrote:
> Kernel kobjects have rigid rules: each container object should be
> dynamically allocated, and can't be allocated into a single kmalloc.
>
> EDAC never obeyed this rule: it has a single malloc function that
> allocates all needed data into a single kzalloc.
>
> As this is not accepted anymore, change the allocation schema of the
> EDAC *_info structs to enforce this Kernel standard.
[]
> diff --git a/drivers/edac/amd64_edac.c b/drivers/edac/amd64_edac.c
[]
> @@ -2228,9 +2228,9 @@ static int init_csrows(struct mem_ctl_info *mci)
> edac_mode = EDAC_NONE;
>
> for (j = 0; j < pvt->channel_count; j++) {
> - csrow->channels[j].dimm->mtype = mtype;
> - csrow->channels[j].dimm->edac_mode = edac_mode;
> - csrow->channels[j].dimm->nr_pages = nr_pages;
> + csrow->channels[j]->dimm->mtype = mtype;
> + csrow->channels[j]->dimm->edac_mode = edac_mode;
> + csrow->channels[j]->dimm->nr_pages = nr_pages;
It might be better to use an automatic for
typeof foo dimm = csrow->channels[j]->dimm;
dimm->mtype = mtype;
etc...
[]
> @@ -293,39 +286,56 @@ struct mem_ctl_info *edac_mc_alloc(unsigned edac_index,
> mci->mem_is_per_rank = per_rank;
>
> /*
> - * Fills the csrow struct
> + * Alocate and fill the csrow/channels structs
> */
> + mci->csrows = kzalloc(sizeof(*mci->csrows) * tot_csrows, GFP_KERNEL);
kcalloc
[]
> + csr->channels = kzalloc(sizeof(*csr->channels) * tot_cschannels,
> + GFP_KERNEL);
here too
> @@ -391,7 +401,31 @@ struct mem_ctl_info *edac_mc_alloc(unsigned edac_index,
>
> trace_hw_event_init("edac", (unsigned)edac_index);
>
> + debugf1("EDAC MCI allocated\n");
> return mci;
> +
> +error:
> + debugf1("Failed to allocate one or more EDAC MCI structs\n");
Generally, it's not necessary to have specific "OOM" messages
as allocations without GFP_NOWARN do dump_stack()s
next prev parent reply other threads:[~2012-04-18 17:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1334608729-30803-1-git-send-email-mchehab@redhat.com>
2012-04-16 20:38 ` [EDAC ABI v13 07/25] edac: Rename the parent dev to pdev Mauro Carvalho Chehab
2012-04-16 20:38 ` [EDAC ABI v13 24/25] edac: change the mem allocation scheme to make Documentation/kobject.txt happy Mauro Carvalho Chehab
2012-04-17 21:17 ` Joe Perches [this message]
2012-04-19 13:14 ` Mauro Carvalho Chehab
2012-04-22 6:37 ` Joe Perches
2012-04-19 13:21 ` [PATCH] " Mauro Carvalho Chehab
2012-04-19 15:28 ` Greg K H
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1334697467.3920.5.camel@joe2Laptop \
--to=joe@perches.com \
--cc=Shaohui.Xie@freescale.com \
--cc=akpm@linux-foundation.org \
--cc=arozansk@redhat.com \
--cc=arvino55@gmail.com \
--cc=borislav.petkov@amd.com \
--cc=cmetcalf@tilera.com \
--cc=dbaryshkov@gmail.com \
--cc=egor@pasemi.com \
--cc=h.mitake@gmail.com \
--cc=jkosina@suse.cz \
--cc=juhlenko@akamai.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mark.gross@intel.com \
--cc=mchehab@redhat.com \
--cc=mmarek@suse.cz \
--cc=norsk5@yahoo.com \
--cc=olof@lixom.net \
--cc=ravi@jetztechnologies.com \
--cc=tim@buttersideup.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).