From: David Teigland <teigland@redhat.com>
To: Jesper Juhl <jj@chaosbits.net>
Cc: "Dr. David Alan Gilbert" <linux@treblig.org>,
linux-kernel@vger.kernel.org
Subject: Re: kmallocs with swapped parameters in fs/dlm/lock.c
Date: Mon, 11 Jul 2011 09:25:11 -0400 [thread overview]
Message-ID: <20110711132511.GB14426@redhat.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1107111032490.4462@swampdragon.chaosbits.net>
On Mon, Jul 11, 2011 at 10:33:20AM +0200, Jesper Juhl wrote:
> On Mon, 11 Jul 2011, Dr. David Alan Gilbert wrote:
>
> > * Jesper Juhl (jj@chaosbits.net) wrote:
> > > On Sun, 10 Jul 2011, Dr. David Alan Gilbert wrote:
> > >
> > > > Hi David,
> > > > Sparse spotted a couple of places in fs/dlm/lock.c where the size/flags
> > > > parameters to kmalloc got swapped:
> > > >
> > > [...]
> > > > Jesper:
> > > > I noticed in your patch:
> > > > https://lkml.org/lkml/2011/7/2/90
> > > >
> > > > where you had done a kmalloc->kzalloc transform you kept the swap.
> > > >
> > > > This looks like new code in 3.0rc so I don't think you could quite
> > > > call it a regression, but it should probably be fixed fairly quickly
> > > > I guess.
> > > >
> > > D'oh, I completely overlooked that.
> >
> > No problem.
> >
> > > Thank you for noticing and letting me know. I've just submitted an updated
> > > patch.
> >
> > Great - it's probably worth you fixing the 2nd case in the same file
> > in the same patch, rather than just the one that you were changing
> > anyway?
> >
> I guess so. I'll update my patch later this evening when I get home from
> work.
I'll wait for your patch(es) before fixing any of these myself.
Thanks,
Dave
next prev parent reply other threads:[~2011-07-11 13:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-10 0:30 kmallocs with swapped parameters in fs/dlm/lock.c Dr. David Alan Gilbert
2011-07-10 20:56 ` Jesper Juhl
2011-07-11 8:25 ` Dr. David Alan Gilbert
2011-07-11 8:33 ` Jesper Juhl
2011-07-11 13:25 ` David Teigland [this message]
2011-07-11 13:23 ` David Teigland
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=20110711132511.GB14426@redhat.com \
--to=teigland@redhat.com \
--cc=jj@chaosbits.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@treblig.org \
/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