[lkml]   [2006]   [Jun]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 2.6.17-rc5-mm3-lockdep - locking error in quotaon

* Jan Kara <> wrote:

> > but that doesn't quite match your description...
> This piece of code is there just because we avoid page cache when
> doing quota writes. That is a different story and should cause problems
> with your lock checker.
> Standard way of running quota is:
> - get i_mutex for data_inode
> - write some data to data_inode
> - requires allocation -> calls DQUOT_ALLOC_SPACE
> - DQUOT_ALLOC_SPACE acquires some quota locks, decides it wants to
> write out quota structure (e.g. because we are journaling quota and
> must preserve quota integrity)
> - acquires dqio_sem, calls filesystem specific quota writing
> function - e.g. ext3_quota_write()
> - this function acquires i_mutex for quota file
> I think this is the type of circle your checker has found.

the validator noticed a circular dependency (AB->BA, or AB->BC->CA,
etc.) - while the nesting above it would report as: "BUG: possible
deadlock detected!".

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2006-06-05 22:18    [W:0.053 / U:2.900 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site