From: Hans Reiser <reiser@namesys.com>
To: Nikita Danilov <Nikita@Namesys.COM>
Cc: Andrew Morton <akpm@digeo.com>,
Linux Kernel Mailing List <Linux-Kernel@Vger.Kernel.ORG>,
Alexander Viro <viro@math.psu.edu>
Subject: Re: locking rules for ->dirty_inode()
Date: Fri, 20 Sep 2002 22:21:22 +0400 [thread overview]
Message-ID: <3D8B6722.8050707@namesys.com> (raw)
In-Reply-To: 15755.23491.712588.305582@laputa.namesys.com
You might ask the SGI guys what they do. I know that they have a
systematic approach to documenting lock ordering.
Hans
next prev parent reply other threads:[~2002-09-20 18:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-20 15:00 locking rules for ->dirty_inode() Nikita Danilov
2002-09-20 15:52 ` Andrew Morton
2002-09-20 16:32 ` Nikita Danilov
2002-09-20 16:47 ` Andrew Morton
2002-09-20 17:32 ` Nikita Danilov
2002-09-20 18:21 ` Hans Reiser [this message]
2002-09-20 22:41 ` Andrew Morton
2002-09-23 16:32 ` Nikita Danilov
2002-09-23 16:42 ` Andrew Morton
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=3D8B6722.8050707@namesys.com \
--to=reiser@namesys.com \
--cc=Linux-Kernel@Vger.Kernel.ORG \
--cc=Nikita@Namesys.COM \
--cc=akpm@digeo.com \
--cc=viro@math.psu.edu \
/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