From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: bugzilla-daemon@bugzilla.kernel.org
Cc: linux-ext4@vger.kernel.org, Mingming <cmm@us.ibm.com>
Subject: Re: [Bug 14739] BUG: scheduling while atomic: nfsd/3369/0x00000002
Date: Mon, 7 Dec 2009 22:39:33 +0530 [thread overview]
Message-ID: <20091207170933.GA16078@skywalker.linux.vnet.ibm.com> (raw)
In-Reply-To: <200912051728.nB5HSDVn018680@demeter.kernel.org>
On Sat, Dec 05, 2009 at 05:28:13PM +0000, bugzilla-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=14739
>
>
> Trond Myklebust <trond.myklebust@fys.uio.no> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |trond.myklebust@fys.uio.no
> Component|NFS |ext4
> AssignedTo|trond.myklebust@fys.uio.no |fs_ext4@kernel-bugs.osdl.or
> | |g
>
>
>
>
> --- Comment #1 from Trond Myklebust <trond.myklebust@fys.uio.no> 2009-12-05 17:28:12 ---
> Hmm... This looks to me like it is rather an ext4 bug. Reassigning to
> the ext4 folks for the moment.
>
Hmm we are doing dquot_reserve_space with i_block_reservation_lock held.
ie
spin_lock(&EXT4_I(inode)->i_block_reservation_lock);
- vfs_dq_reserve_block
- down_read(&sb_dqopt(inode->i_sb)->dqptr_sem)
Adding Mingming to CC:
-aneesh
next prev parent reply other threads:[~2009-12-07 17:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-14739-13602@http.bugzilla.kernel.org/>
2009-12-05 17:28 ` [Bug 14739] BUG: scheduling while atomic: nfsd/3369/0x00000002 bugzilla-daemon
2009-12-07 17:09 ` Aneesh Kumar K.V [this message]
2009-12-07 17:09 ` bugzilla-daemon
2009-12-11 12:11 ` bugzilla-daemon
[not found] <bug-14739-13602@https.bugzilla.kernel.org/>
2012-06-18 13:05 ` bugzilla-daemon
2012-06-18 13:05 ` bugzilla-daemon
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=20091207170933.GA16078@skywalker.linux.vnet.ibm.com \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=cmm@us.ibm.com \
--cc=linux-ext4@vger.kernel.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 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).