public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Tinguely <tinguely@sgi.com>
To: Vlad Bespalov <vlad.botanic@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: possible null pointer in xlog_iodone
Date: Fri, 14 Jun 2013 14:42:01 -0500	[thread overview]
Message-ID: <51BB7209.6040301@sgi.com> (raw)
In-Reply-To: <CA+aXbB5ohJkDde8qJSE0AU6B0dh59YjNPVfxVjXCOg73k7ihXQ@mail.gmail.com>

On 06/14/13 12:15, Vlad Bespalov wrote:
> i`m running an xfs filesystem over device going offline/online and
> sometimes offline may be done in parallel with unmounting
>
> at some point i got several crashes with null pointer panic in
> xlog_iodone: xlog_t structure taken from input buffer is null
>
> i wonder if the following call path combined with disk online/offline
> handling could have led to this crash:
>
> --------------
> xfs_unmountfs()
>      xfs_log_unmount_write(mp)
>          xlog_state_release_iclog(log)
>              xlog_sync(log, iclog = log->l_iclog)
>              (bp=iclog->ic_bp)
>                  xlog_bdstrat(bp)
>                  (iclog->ic_state != XLOG_STATE_ERROR ? )
>                      xfs_buf_iorequest(bp)
>                          xfs_buf_ioend (called with scheduling (*) )
>                          (queues  : bp->b_iodone_work,
>                           callback: xlog_iodone)
>      xfs_log_unmount(mp)
>          xfs_trans_ail_destroy(mp);
>          xlog_dealloc_log(mp->m_log); /*frees and nullifies all iclog->ic_log*/
> -----------
>
> (after we`ve cleaned up log structures we switch processes*)
>      xlog_iodone(bp)
>      {
>          iclog = bp->private
>          l = iclog->ic_log
>          if (XFS_TEST_ERROR((XFS_BUF_GETERROR(bp)), l->l_mp,
>                          XFS_ERRTAG_IODONE_IOERR, XFS_RANDOM_IODONE_IOERR))
>          {
>
>                      xfs_buf_ioerror_alert(bp, __func__);
>                      XFS_BUF_STALE(bp);
> /*l ?= NULL*/ xfs_force_shutdown(l->l_mp, SHUTDOWN_LOG_IO_ERROR);
>          }
>      }
>
>
> Thanks for your time.
> Best regards,
> Vlad Bespalov.
>

Hi,

Looks like the log unmount record can't get written because of the disk 
being offline.

When the write times out, the log structures are long gone.

I bet if you used memory poisoning, the iclog->ic_log would not work either.

--Mark.

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2013-06-14 19:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-14 17:15 possible null pointer in xlog_iodone Vlad Bespalov
2013-06-14 19:42 ` Mark Tinguely [this message]
2013-06-15  1:03 ` Dave Chinner
2013-06-17 14:38   ` Vlad Bespalov
2013-06-18  0:19     ` Dave Chinner
2013-06-18  0:37       ` Vlad Bespalov

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=51BB7209.6040301@sgi.com \
    --to=tinguely@sgi.com \
    --cc=vlad.botanic@gmail.com \
    --cc=xfs@oss.sgi.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