mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: bsuparna@in.ibm.com
To: "David S. Miller" <davem@redhat.com>
Cc: torvalds@transmeta.com, aviro@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: Oddness in i_shared_lock and page_table_lock nesting hierarchies ?
Date: Thu, 9 Nov 2000 17:46:53 +0530	[thread overview]
Message-ID: <CA256992.004406D2.00@d73mta05.au.ibm.com> (raw)


 > The fix we agreed on back then is easy (make rest of kernel match
 > vmtruncate()'s locking order), it just takes time to implement and
 > test.

  David,

  I was looking into the vmm code and trying to work out exactly how to fix
this, and there are
  some questions in my mind - mainly a few cases (involving multiple vma
updates) which
  I'm not sure about the cleanest way to tackle.
  But before I bother anyone with those, I thought I ought to go through
the earlier discussions
  that you had while coming up with what the fix should be. Maybe you've
already gone over
  this once.
  Could you point me to those ? Somehow I haven't been successful in
locating them.

  Regards
  Suparna


  Suparna Bhattacharya
  Systems Software Group, IBM Global Services, India
  E-mail : bsuparna@in.ibm.com
  Phone : 91-80-5267117, Extn : 2525




-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

             reply	other threads:[~2000-11-09 12:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-09 12:16 bsuparna [this message]
2000-11-10  6:44 ` David S. Miller
  -- strict thread matches above, loose matches on Subject: below --
2000-11-10  9:29 bsuparna
2000-11-10  6:55 aprasad
2000-11-10  7:34 ` David S. Miller
2000-11-06 13:50 bsuparna
2000-11-05  5:51 bsuparna
2000-11-06  3:14 ` David S. Miller
2000-11-06 18:42 ` tytso

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=CA256992.004406D2.00@d73mta05.au.ibm.com \
    --to=bsuparna@in.ibm.com \
    --cc=aviro@redhat.com \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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

all inboxes | Powered by JetHome®