linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Grissiom <chaos.proton@gmail.com>
To: "Dave Kleikamp" <shaggy@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org,
	"Arjan van de Ven" <arjan@infradead.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: "BUG: scheduling while atomic: pdflush/30/0x00000002" in latest git
Date: Fri, 9 Jan 2009 13:18:14 +0800	[thread overview]
Message-ID: <a0adeea50901082118g543aec82ifc574291ab0592d5@mail.gmail.com> (raw)
In-Reply-To: <1231425472.21528.13.camel@norville.austin.ibm.com>

On Thu, Jan 8, 2009 at 22:37, Dave Kleikamp <shaggy@linux.vnet.ibm.com> wrote:
>
> The offender is
> http://git.kernel.org/gitweb.cgi?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=efaee192
>
> async_synchronize_full_special() shouldn't be called while holding a
> spinlock, sb_lock.
>
> I think this patch should fix it.  Arjan, would this work?
>
> Signed-off-by: Dave Kleikamp <shaggy@linux.vnet.ibm.com>
>
> diff --git a/fs/super.c b/fs/super.c
> index cb20744..7d67387 100644
> --- a/fs/super.c
> +++ b/fs/super.c
> @@ -458,7 +458,6 @@ void sync_filesystems(int wait)
>                if (sb->s_flags & MS_RDONLY)
>                        continue;
>                sb->s_need_sync_fs = 1;
> -               async_synchronize_full_special(&sb->s_async_list);
>        }
>
>  restart:
> @@ -471,6 +470,7 @@ restart:
>                sb->s_count++;
>                spin_unlock(&sb_lock);
>                down_read(&sb->s_umount);
> +               async_synchronize_full_special(&sb->s_async_list);
>                if (sb->s_root && (wait || sb->s_dirt))
>                        sb->s_op->sync_fs(sb, wait);
>                up_read(&sb->s_umount);
>
> --
> David Kleikamp
> IBM Linux Technology Center
>
>

Problem gone with this patch applied. Thanks for the fixing.

-- 
Cheers,
Grissiom

      parent reply	other threads:[~2009-01-09  5:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <a0adeea50901080007q5a3ed5c8y5a744ce37e677325@mail.gmail.com>
2009-01-08 14:37 ` "BUG: scheduling while atomic: pdflush/30/0x00000002" in latest git Dave Kleikamp
2009-01-08 15:21   ` Arjan van de Ven
2009-01-08 15:46     ` [PATCH] async: Don't call async_synchronize_full_special() while holding sb_lock Dave Kleikamp
2009-01-08 22:50       ` Dave Chinner
2009-01-08 22:51         ` Arjan van de Ven
2009-01-09  0:32           ` Alan Cox
2009-01-09  0:38             ` Arjan van de Ven
2009-01-09  1:40           ` Dave Chinner
2009-01-09  4:45             ` Arjan van de Ven
2009-01-09  8:22               ` Dave Chinner
2009-01-09 15:09                 ` Chris Mason
2009-01-12  2:31               ` Jamie Lokier
2009-01-12  3:54                 ` Arjan van de Ven
2009-01-12  7:55                   ` Dave Chinner
2009-01-12  7:48                 ` Dave Chinner
2009-01-09 12:31         ` Evgeniy Polyakov
2009-01-09  5:18   ` Grissiom [this message]

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=a0adeea50901082118g543aec82ifc574291ab0592d5@mail.gmail.com \
    --to=chaos.proton@gmail.com \
    --cc=arjan@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shaggy@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).