reiserfs-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: reiserfs-devel@vger.kernel.org
Subject: [Bug 34362] New: Error-valued pointer dereferences
Date: Wed, 4 May 2011 12:46:16 GMT	[thread overview]
Message-ID: <bug-34362-695@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=34362

           Summary: Error-valued pointer dereferences
           Product: File System
           Version: 2.5
    Kernel Version: 2.6.38.3
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: ReiserFS
        AssignedTo: reiserfs-devel@vger.kernel.org
        ReportedBy: crubio@cs.wisc.edu
        Regression: No


Created an attachment (id=56552)
 --> (https://bugzilla.kernel.org/attachment.cgi?id=56552)
Sample traces describing error-valued pointer dereferences

We have statically analyzed ReiserFS, VFS and the memory management module to
find error-valued pointers that are dereferenced. We have found five potential
error-valued pointer dereferences:

fs/inode.c:1436: Dereferencing variable iput#inode, which may contain one of
the following error codes: ENOMEM* 

fs/reiserfs/super.c:249: Dereferencing variable finish_unfinished#inode, which
may contain one of the following error codes: ENOMEM* 

fs/reiserfs/super.c:259: Dereferencing variable finish_unfinished#inode, which
may contain one of the following error codes: ENOMEM* 

fs/reiserfs/super.c:279: Dereferencing variable finish_unfinished#inode, which
may contain one of the following error codes: ENOMEM* 

fs/super.c:205: Dereferencing variable deactivate_super#s, which may contain
one of the following error codes: ENOMEM* 


For each potential error-valued pointer dereference, our tool produces a
complete sample trace and the corresponding slice. The complete sample trace
illustrates how one error code may reach the program point at which the
variable is dereferenced. The slice summarizes the complete sample trace by
including only relevant program points at which the error code is transferred
from variable to variable or returned by a function. Sample traces and slices
are attached.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

             reply	other threads:[~2011-05-04 12:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-04 12:46 bugzilla-daemon [this message]
2014-06-25 15:46 ` [Bug 34362] Error-valued pointer dereferences bugzilla-daemon
2015-02-19 16:24 ` bugzilla-daemon
2016-03-23 18:12 ` bugzilla-daemon

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=bug-34362-695@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=reiserfs-devel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).