From: Torsten Hilbrich <torsten.hilbrich@secunet.com>
To: linux-kernel@vger.kernel.org
Cc: "Andreas Bießmann" <biessmann@corscience.de>,
"Hilbrich, Torsten" <Torsten.Hilbrich@secunet.com>,
"Sergey Senozhatsky" <sergey.senozhatsky@gmail.com>
Subject: Re: [PATCH] fs-writeback: fix NULL pointer dereference in, __mark_inode_dirty
Date: Thu, 10 Mar 2011 11:39:46 +0100 [thread overview]
Message-ID: <4D78AA72.3060202@secunet.com> (raw)
In-Reply-To: fa.8ND6HoGS9dKYUuniFCAoNq+1TFY@ifi.uio.no
I ran into the same problem and successfully applied your fix.
I was able to reproduce this panic and bisected it to the following commit:
commit aaead25b954879e1a708ff2f3602f494c18d20b5
Author: Christoph Hellwig <hch@lst.de>
Date: Mon Oct 4 14:25:33 2010 +0200
writeback: always use sb->s_bdi for writeback purposes
The steps to reproduce it on my test system (T60p with Intel Core Duo) were.
- /dev/sdb is an USB stick with partition sdb1 formatted as ext2
- mount /dev/sdb1 /mnt
- cat > /mnt/foo
- now press return some times
- remove stick
- press return, panic takes place
Hope this helps fixing the problem,
Torsten
next parent reply other threads:[~2011-03-10 10:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.8ND6HoGS9dKYUuniFCAoNq+1TFY@ifi.uio.no>
2011-03-10 10:39 ` Torsten Hilbrich [this message]
2011-03-15 10:17 ` [PATCH] fs-writeback: fix NULL pointer dereference in, __mark_inode_dirty Torsten Hilbrich
2011-03-15 12:11 ` Anton Altaparmakov
2011-03-15 12:35 ` Jens Axboe
2011-03-15 12:40 ` Torsten Hilbrich
2011-02-28 15:25 [PATCH] fs-writeback: fix NULL pointer dereference in __mark_inode_dirty Andreas Bießmann
2011-02-28 15:43 ` Sergey Senozhatsky
2011-02-28 15:59 ` Andreas Bießmann
2011-02-28 16:29 ` Sergey Senozhatsky
[not found] ` <AANLkTimARkrtmBBgtXmNA=MOD94FWQ8x-qcmLJ8mdQ6o@mail.gmail.com>
2011-03-02 8:35 ` Andreas Bießmann
2011-03-02 8:35 ` Andreas Bießmann
2011-03-03 13:58 ` Andreas Bießmann
2011-03-03 13:58 ` Andreas Bießmann
2011-03-17 21:04 ` Andrew Morton
2011-03-17 21:06 ` George Spelvin
2011-03-17 22:19 ` Sergey Senozhatsky
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=4D78AA72.3060202@secunet.com \
--to=torsten.hilbrich@secunet.com \
--cc=biessmann@corscience.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sergey.senozhatsky@gmail.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 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.