mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Peter Osterlund <petero2@telia.com>,
	viro@parcelfarce.linux.theplanet.co.uk,
	linux-kernel@vger.kernel.org, axboe@suse.de
Subject: Re: [PATCH] CDRW packet writing support for 2.6.7-bk13
Date: Fri, 2 Jul 2004 15:47:20 -0700	[thread overview]
Message-ID: <20040702224720.GA7969@kroah.com> (raw)
In-Reply-To: <20040702150819.646b6103.akpm@osdl.org>

On Fri, Jul 02, 2004 at 03:08:19PM -0700, Andrew Morton wrote:
> Peter Osterlund <petero2@telia.com> wrote:
> >
> > This code leaks a module reference. The patch below fixes it. I'm not
> > sure it's correct, but do_open() also does module_put() after
> > put_disk().
> > 
> > Signed-off-by: Peter Osterlund <petero2@telia.com>
> > 
> > ---
> > 
> >  linux-petero/fs/partitions/check.c |    1 +
> >  1 files changed, 1 insertion(+)
> > 
> > diff -puN fs/partitions/check.c~packet-refcnt fs/partitions/check.c
> > --- linux/fs/partitions/check.c~packet-refcnt	2004-07-02 23:18:22.000000000 +0200
> > +++ linux-petero/fs/partitions/check.c	2004-07-02 23:18:23.000000000 +0200
> > @@ -151,6 +151,7 @@ const char *__bdevname(dev_t dev, char *
> >  	if (disk) {
> >  		buffer = disk_name(disk, part, buffer);
> >  		put_disk(disk);
> > +		module_put(disk->fops->owner);
> >  	} else {
> >  		snprintf(buffer, BDEVNAME_SIZE, "unknown-block(%u,%u)",
> >  				MAJOR(dev), MINOR(dev));
> 
> Yes, there's certainly a leak there.  It's surprising that it hasn't been
> noted before.
> 
> But:
> 
> const char *__bdevname(dev_t dev, char *buffer)
> {
> 	struct gendisk *disk;
> 	int part;
> 
> 	disk = get_gendisk(dev, &part);
> 	if (disk) {
> 		buffer = disk_name(disk, part, buffer);
> 		put_disk(disk);
> 	} else {
> 		snprintf(buffer, BDEVNAME_SIZE, "unknown-block(%u,%u)",
> 				MAJOR(dev), MINOR(dev));
> 	}
> 
> get_gendisk() did an internal module_get() in kobj_lookup().

But if kobj_lookup() succeeds, module_put() is called before returning
(actually it's always called, right?) 

> It would seem to be logical that the module_put() should be in
> kobject_put(), called from put_disk().  But surely if we made that
> change 1000 things would explode.

I don't see how that would fix anything, as the module reference is not
held after kobj_lookup() returns.  Or am I missing something here?

thanks,

greg k-h

  reply	other threads:[~2004-07-02 22:48 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-01 13:34 Peter Osterlund
2004-07-02 21:52 ` Peter Osterlund
2004-07-02 22:08   ` Andrew Morton
2004-07-02 22:47     ` Greg KH [this message]
2004-07-02 22:59       ` Andrew Morton
2004-07-02 23:24         ` Peter Osterlund
2004-07-02 23:51           ` Andrew Morton
2004-07-04 11:57             ` Peter Osterlund
2004-07-04 20:58               ` Andrew Morton
2004-07-04 21:06                 ` Christoph Hellwig
2004-07-04 12:30 ` [PATCH] Fix race in pktcdvd kernel thread handling Peter Osterlund
2004-07-04 12:37 ` [PATCH] Fix open/close races in pktcdvd Peter Osterlund
2004-07-04 13:05 ` [PATCH] CDRW packet writing support for 2.6.7-bk13 Christoph Hellwig
2004-07-04 23:49   ` Peter Osterlund
2004-07-05  0:01     ` Peter Osterlund
2004-07-10 23:20       ` Arnd Bergmann
2004-07-10 23:27         ` Christoph Hellwig
2004-07-11  1:06           ` Peter Osterlund
2004-07-12 16:25             ` Arnd Bergmann
2004-07-12 16:34               ` Christoph Hellwig
2004-07-13  6:04                 ` Jens Axboe
2004-07-14  0:06             ` [RFC][PATCH] Control pktcdvd with an auxiliary character device Peter Osterlund
2004-07-14  0:17               ` Peter Osterlund
2004-07-05  8:17     ` [PATCH] CDRW packet writing support for 2.6.7-bk13 Jens Axboe
2004-07-05 10:26     ` Christoph Hellwig
2004-07-06  8:45     ` Peter Osterlund
2004-07-07 10:06   ` Peter Osterlund

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=20040702224720.GA7969@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@osdl.org \
    --cc=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=petero2@telia.com \
    --cc=viro@parcelfarce.linux.theplanet.co.uk \
    /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

Powered by JetHome