From: Dan Carpenter <dan.carpenter@oracle.com>
To: Alessandro Rubini <rubini@gnudd.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [patch] FMC: NULL dereference on allocation failure
Date: Wed, 19 Jun 2013 18:57:32 +0300 [thread overview]
Message-ID: <20130619155731.GA4957@mwanda> (raw)
In-Reply-To: <20130619152528.GA16430@mail.gnudd.com>
On Wed, Jun 19, 2013 at 05:25:28PM +0200, Alessandro Rubini wrote:
> > If we don't allocate "arr" then the cleanup path will dereference it and
> > oops.
>
> You are right, thanks (acked).
>
> How is the procedure here? I don't have my own git tree on
> kernel.org for pull requests. Can this go through the janitors?
>
> (if it makes sense, I can try the procedure to have a tree, but last
> time I checked it was strictly denied to anyone).
Apparently these are going through Greg K-H. I'll resend, with Greg
CC'd so he can pick it up from the mailing list.
Could you add an entry to the MAINTAINERS file so that Greg will be
CC'd automatically using get_maintainer.pl? Is there a dedicated
list for FMC development? That would go in the MAINTAINERS file as
well.
regards,
dan carpenter
next prev parent reply other threads:[~2013-06-19 15:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 14:49 [patch] FMC: NULL dereference on allocation failure Dan Carpenter
2013-06-19 15:25 ` Alessandro Rubini
2013-06-19 15:57 ` Dan Carpenter [this message]
2013-06-19 16:01 ` [patch -next] " Dan Carpenter
2013-06-19 16:15 ` Joe Perches
2013-06-19 17:57 ` Alessandro Rubini
2013-06-19 18:09 ` Joe Perches
2013-06-20 8:06 ` Dan Carpenter
2013-06-19 17:57 ` [patch] " Alessandro Rubini
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=20130619155731.GA4957@mwanda \
--to=dan.carpenter@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rubini@gnudd.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