From: Torsten Hilbrich <torsten.hilbrich@secunet.com>
To: Anton Altaparmakov <aia21@cam.ac.uk>
Cc: LKML <linux-kernel@vger.kernel.org>,
"Andreas Bießmann" <biessmann@corscience.de>,
"Sergey Senozhatsky" <sergey.senozhatsky@gmail.com>,
"Christoph Hellwig" <hch@lst.de>, "Jens Axboe" <axboe@kernel.dk>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH] fs-writeback: fix NULL pointer dereference in, __mark_inode_dirty
Date: Tue, 15 Mar 2011 13:40:11 +0100 [thread overview]
Message-ID: <4D7F5E2B.6090805@secunet.com> (raw)
In-Reply-To: <99773600-FC41-41A9-8544-BF7E09065546@cam.ac.uk>
On 15.03.2011 13:11, Anton Altaparmakov wrote:
> This is already being handled. It is the same as other bug reports, i.e. the fact that sb->s_bdi is made NULL on device removal and if it happens at the wrong time you then get a NULL pointer dereference.
>
> Jens Axboe just only yesterday posted an initial patch for this. Can you please test it and report back if it does indeed cure the problem?
>
> The patch can be found here for example:
>
> https://lkml.org/lkml/2011/3/14/25
>
This patch fixes the problem for my test szenario.
Torsten
next prev parent reply other threads:[~2011-03-15 12:41 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 ` [PATCH] fs-writeback: fix NULL pointer dereference in, __mark_inode_dirty Torsten Hilbrich
2011-03-15 10:17 ` Torsten Hilbrich
2011-03-15 12:11 ` Anton Altaparmakov
2011-03-15 12:35 ` Jens Axboe
2011-03-15 12:40 ` Torsten Hilbrich [this message]
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=4D7F5E2B.6090805@secunet.com \
--to=torsten.hilbrich@secunet.com \
--cc=aia21@cam.ac.uk \
--cc=axboe@kernel.dk \
--cc=biessmann@corscience.de \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=torvalds@linux-foundation.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.