From: Dan Carpenter <dan.carpenter@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] ocfs2/cluster: Clean up messages in o2net
Date: Thu, 9 Aug 2012 15:22:05 +0300 [thread overview]
Message-ID: <20120809122205.GD3683@mwanda> (raw)
In-Reply-To: <4E5D529C.5020706@oracle.com>
This is still here. I'm not sure why this error message just showed
up in linux-next again. Odd.
regards,
dan carpenter
On Tue, Aug 30, 2011 at 02:14:04PM -0700, Sunil Mushran wrote:
> Thanks. I'll fix the two.
>
> On 08/25/2011 06:01 PM, Dan Carpenter wrote:
> >Hello Sunil Mushran,
> >
> >1dfecf810e0e: "ocfs2/cluster: Clean up messages in o2net"
> >Leads to the following Smatch complaint:
> >fs/ocfs2/cluster/tcp.c +1704 o2net_start_connect(101)
> > error: we previously assumed 'sc' could be null (see line 1650)
> >
> >fs/ocfs2/cluster/tcp.c
> > 1649 sc = sc_alloc(node);
> > 1650 if (sc == NULL) {
> > 1651 mlog(0, "couldn't allocate sc\n");
> > 1652 ret = -ENOMEM;
> > 1653 goto out;
> > 1654 }
> > 1655
> >
> >--- [snip] ---
> >
> > 1701 out:
> > 1702 if (ret) {
> > 1703 printk(KERN_NOTICE "o2net: Connect attempt to " SC_NODEF_FMT
> > 1704 " failed with errno %d\n", SC_NODEF_ARGS(sc), ret);
> > ^^
> >Null dereference here.
> >
> > 1705 /* 0 err so that another will be queued and attempted
> > 1706 * from set_nn_state */
> >
> >This email is from my new semi-automatic bug reporting tool script.
> >Btw, Smatch complains about this as well:
> >
> >fs/ocfs2/cluster/tcp.c +549 o2net_set_nn_state(44)
> > error: we previously assumed 'old_sc' could be null (see line 517)
> >
> >These dereferences were disabled in my old config, but Smatch detects
> >them now that we're using normal printk()
> >
> >regards,
> >dan carpenter
next prev parent reply other threads:[~2012-08-09 12:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110826010109.GA27582@shale.localdomain>
2011-08-30 21:14 ` [Ocfs2-devel] ocfs2/cluster: Clean up messages in o2net Sunil Mushran
2012-08-09 12:22 ` Dan Carpenter [this message]
2012-08-15 18:03 ` Sunil Mushran
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=20120809122205.GD3683@mwanda \
--to=dan.carpenter@oracle.com \
--cc=ocfs2-devel@oss.oracle.com \
/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