mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dawson Engler <engler@csl.Stanford.EDU>
To: adilger@clusterfs.com (Andreas Dilger)
Cc: linux-kernel@vger.kernel.org, mc@cs.Stanford.EDU
Subject: Re: [CHECKER] 54 missing null pointer checks in 2.4.17
Date: Sun, 9 Jun 2002 23:07:05 -0700 (PDT)	[thread overview]
Message-ID: <200206100607.XAA17282@csl.Stanford.EDU> (raw)
In-Reply-To: <20020610052807.GB20388@turbolinux.com> from "Andreas Dilger" at Jun 09, 2002 11:28:07 PM

> > /u2/engler/mc/oses/linux/2.4.17/fs/jbd/journal.c
> > 	 * Do we need to do a data copy?
> > 	 */
> > 
> > 	if (need_copy_out && !done_copy_out) {
> > 		char *tmp;
> > Start --->
> > 		tmp = jbd_rep_kmalloc(jh2bh(jh_in)->b_size, GFP_NOFS);
> > 
> > 		jh_in->b_frozen_data = tmp;
> > Error --->
> > 		memcpy (tmp, mapped_data, jh2bh(jh_in)->b_size);
> 
> Note that jbd_rep_kmalloc() is a special case, and will not currently
> return NULL.  This macro calls  __jbd_rep_kmalloc(..., retry=1) which
> means "repeat the allocation until it succeeds" so the code path
> "if (!retry) return NULL" can never actually happen from this caller.
> The logic is somewhat convoluted, so it is not surprising that the
> checker didn't distinguish this case (it would have to have done the
> "constant" evaluation to drop the NULL return path from the code).

Interesting.  The checker infers which functions can plausibly return
null by counting, for each function f:
	1.  how many callsites check f's return value against null
 versus 
	2.how many do not.  
In this case the reason we were checking jbd_rep_kmalloc (actually
__jbd_kmalloc) was because five other callers in jbd checked it:

/u2/engler/mc/oses/linux/2.4.17/fs/jbd/journal.c:695:journal_init_common: NOTE:NULL:692:695:[EXAMPLE=__jbd_kmalloc:692]
/u2/engler/mc/oses/linux/2.4.17/fs/jbd/transaction.c:54:get_transaction: NOTE:NULL:50:54:[EXAMPLE=__jbd_kmalloc:50]
/u2/engler/mc/oses/linux/2.4.17/fs/jbd/transaction.c:233:journal_start: NOTE:NULL:230:233:[EXAMPLE=__jbd_kmalloc:230]
/u2/engler/mc/oses/linux/2.4.17/fs/jbd/transaction.c:339:journal_try_start: NOTE:NULL:336:339:[EXAMPLE=__jbd_kmalloc:336]
/u2/engler/mc/oses/linux/2.4.17/fs/jbd/transaction.c:895:journal_get_undo_access: NOTE:NULL:885:895:[EXAMPLE=__jbd_kmalloc:885]

which means there are indeed bugs in jbd, just not the one we flagged ;-)

Dawson

PS this is the meaning of the rather opaque "[ex=5] [counter=1]" in the
error message:  5 checks of __jbd_kmalloc versus 1 use-without-check of it.

/u2/engler/mc/oses/linux/2.4.17/fs/jbd/journal.c:441:journal_write_metadata_buffer: ERROR:NULL:438:441:Passing unknown ptr "tmp"! as arg 0 to call "memcpy"! set by '__jbd_kmalloc':438 [COUNTER=__jbd_kmalloc:438] [fit=22] [fit_fn=1] [fn_ex=0] [fn_counter=1] [ex=5] [counter=1] [z = -1.31122013621437] [fn-z = -4.35889894354067]

  reply	other threads:[~2002-06-10  6:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-10  3:55 Dawson Engler
2002-06-10  5:22 ` Kasper Dupont
2002-06-10  5:56   ` Dawson Engler
2002-06-10  5:28 ` Andreas Dilger
2002-06-10  6:07   ` Dawson Engler [this message]
2002-06-10  6:35     ` Andreas Dilger
2002-06-10  7:05       ` Dawson Engler
2002-06-10  7:19     ` Giuliano Pochini
2002-06-10 12:40       ` john slee
2002-06-10  7:03 ` Brad Hards
2002-06-10  7:08   ` Dawson Engler
2002-06-11  0:30 ` Greg KH

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=200206100607.XAA17282@csl.Stanford.EDU \
    --to=engler@csl.stanford.edu \
    --cc=adilger@clusterfs.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mc@cs.Stanford.EDU \
    /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®