mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Oliver Pinter <oliver.pntr@gmail.com>
Cc: Willy Tarreau <w@1wt.eu>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Abdel Benamrouche <draconux@gmail.com>,
	stable@kernel.org, jens.axboe@oracle.com,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC, 2.6.26.2-rc1] fs/partition/check.c: fix return value warning
Date: Sun, 03 Aug 2008 13:12:08 +0200	[thread overview]
Message-ID: <48959288.4040108@s5r6.in-berlin.de> (raw)
In-Reply-To: <6101e8c40808021309r7de3cd31r11eb707b14c92fc4@mail.gmail.com>

Oliver Pinter wrote:
> Willy, this good to know ...
> 
> and I think, this patch fixed a small leak:
> 
> +
> +out2:
> +       device_del(&p->dev);
> +out1:
> +       put_device(&p->dev);
> +       free_part_stats(p);
> +out0:
> +       kfree(p);
> +       return err;
> 
> 
> On 8/2/08, Willy Tarreau <w@1wt.eu> wrote:
>> On Sat, Aug 02, 2008 at 12:56:10PM -0700, Linus Torvalds wrote:
>>> Please don't just send patches to the stable team because they "look
>>> fine". They should be real bugs, with real consequences. And no, a
>>> compiler warning is not a real consequence.

Oliver, check under which circumstances the leak happens, and which 
problems the leak causes for the system.

Newly added failure handling paths, which by nature are insufficiently 
runtime-tested, need to be well considered before they are taken over 
into -stable even if the code looks OK.  I.e. they need to address bugs 
which are known to cause problems of certain severity in practice.
-- 
Stefan Richter
-=====-==--- =--- ---==
http://arcgraph.de/sr/

      reply	other threads:[~2008-08-03 11:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-02 20:02 Oliver Pinter
2008-08-02 19:56 ` Linus Torvalds
2008-08-02 20:04   ` Willy Tarreau
2008-08-02 20:09     ` Oliver Pinter
2008-08-03 11:12       ` Stefan Richter [this message]

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=48959288.4040108@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=akpm@linux-foundation.org \
    --cc=draconux@gmail.com \
    --cc=jens.axboe@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oliver.pntr@gmail.com \
    --cc=stable@kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=w@1wt.eu \
    /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

all inboxes | Powered by JetHome®