All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Sebastian Siewior <lkml@ml.breakpoint.cc>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG] panic after umount (biscted)
Date: Fri, 26 Oct 2007 11:27:24 +0200	[thread overview]
Message-ID: <20071026092724.GC5155@kernel.dk> (raw)
In-Reply-To: <20071026070110.GA8927@Chamillionaire.breakpoint.cc>

On Fri, Oct 26 2007, Sebastian Siewior wrote:
> After umount of 
> /dev/md/1 on /mnt/sec type xfs (rw,nosuid,nodev,noatime,nodiratime)
> 
> I end up with [1] on v2.6.24-rc1. It worked fine with v2.6.23. Bisec
> came to conclusion that 
> 
> |fd5d806266935179deda1502101624832eacd01f is first bad commit
> |commit fd5d806266935179deda1502101624832eacd01f
> |Author: Jens Axboe <jens.axboe@oracle.com>
> |Date:   Tue Oct 16 11:05:02 2007 +0200
> |
> |    block: convert blkdev_issue_flush() to use empty barriers
> |    
> |    Then we can get rid of ->issue_flush_fn() and all the driver private
> |    implementations of that.
> |    
> |    Signed-off-by: Jens Axboe <jens.axboe@oracle.com>
> |
> |:040000 040000 75f5c511fd785fa4c75b955f1818c382593a22ec adf460e288740ca9c0b5ab823dfc2ca04980f3d2 M      block
> |:040000 040000 a972fe9a2433a00c79fd5ead584c482cd08b4b2c 0f4534094b63fe21c5cf8a6170736abe5c518c00 M      drivers
> |:040000 040000 ba2a9f681826db89ba5192a7db7139baecde786a fc68a77a41d25c283f39f712216566e9b36d00fc M      include
> 
> is the bad boy here.
> The last panic (with first bad commit) is [2] (there is almost no 
> difference). My .config [3], lspci [4], bisec-log [5]. The md1 
> raid is a
> 
> |Personalities : [raid1] 
> |md1 : active raid1 sda2[1]
> |      174843328 blocks [2/1] [_U]
> |
> 
> I hope this was usefull. Now, I'm going to rebuild my raid now....
> 
> [1] http://download.breakpoint.cc/bug/bug_rc1.jpeg 166 KiB
> [2] http://download.breakpoint.cc/bug/bug_last_commit.jpeg 217 KiB
> [3] http://download.breakpoint.cc/bug/config.txt 27 KiB
> [4] http://download.breakpoint.cc/bug/lspci.txt 2.3 KiB
> [5] http://download.breakpoint.cc/bug/git-bisect-log.txt 2.3K

Thanks a lot, a full report on this issue. Will get this fixed up asap.

-- 
Jens Axboe


  reply	other threads:[~2007-10-26  9:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-26  7:01 [BUG] panic after umount (biscted) Sebastian Siewior
2007-10-26  9:27 ` Jens Axboe [this message]
2007-10-26  9:32   ` Jens Axboe
2007-10-26 11:35     ` Sebastian Siewior
2007-10-26 11:42       ` Jens Axboe
2007-10-27 10:44         ` Sebastian Siewior
2007-10-27 11:39           ` Jens Axboe
2007-10-27 17:56             ` Sebastian Siewior

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=20071026092724.GC5155@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@ml.breakpoint.cc \
    /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.