All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: lustre-devel@lists.lustre.org
Subject: [lustre-devel] [bug report] staging: lustre: clio: Revise read ahead implementation
Date: Thu, 20 Oct 2016 14:17:36 +0300	[thread overview]
Message-ID: <20161020105747.GA7003@elgon.mountain> (raw)

Hello Jinshan Xiong,

The patch 1e1db2a97be5: "staging: lustre: clio: Revise read ahead
implementation" from Oct 2, 2016, leads to the following static
checker warning:

	drivers/staging/lustre/lustre/lov/lov_io.c:611 lov_io_read_ahead()
	error: 'sub' dereferencing possible ERR_PTR()

drivers/staging/lustre/lustre/lov/lov_io.c
   589  static int lov_io_read_ahead(const struct lu_env *env,
   590                               const struct cl_io_slice *ios,
   591                               pgoff_t start, struct cl_read_ahead *ra)
   592  {
   593          struct lov_io *lio = cl2lov_io(env, ios);
   594          struct lov_object *loo = lio->lis_object;
   595          struct cl_object *obj = lov2cl(loo);
   596          struct lov_layout_raid0 *r0 = lov_r0(loo);
   597          unsigned int pps; /* pages per stripe */
   598          struct lov_io_sub *sub;
   599          pgoff_t ra_end;
   600          loff_t suboff;
   601          int stripe;
   602          int rc;
   603  
   604          stripe = lov_stripe_number(loo->lo_lsm, cl_offset(obj, start));
   605          if (unlikely(!r0->lo_sub[stripe]))
   606                  return -EIO;
   607  
   608          sub = lov_sub_get(env, lio, stripe);
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Do we need error handling here?

   609  
   610          lov_stripe_offset(loo->lo_lsm, cl_offset(obj, start), stripe, &suboff);
   611          rc = cl_io_read_ahead(sub->sub_env, sub->sub_io,
   612                                cl_index(lovsub2cl(r0->lo_sub[stripe]), suboff),
   613                                ra);
   614          lov_sub_put(sub);
   615  

regards,
dan carpenter

             reply	other threads:[~2016-10-20 11:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-20 11:17 Dan Carpenter [this message]
2016-10-20 14:43 ` [lustre-devel] [bug report] staging: lustre: clio: Revise read ahead implementation Giedrius Statkevičius
2016-10-20 19:20   ` Dan Carpenter
2016-10-20 14:50 ` Xiong, Jinshan

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=20161020105747.GA7003@elgon.mountain \
    --to=dan.carpenter@oracle.com \
    --cc=lustre-devel@lists.lustre.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.