From: David Miller <davem@davemloft.net>
To: greearb@candelatech.com
Cc: bhutchings@solarflare.com, netdev@vger.kernel.org
Subject: Re: Question on ipmr.c locking in 2.6.25
Date: Thu, 29 May 2008 03:47:28 -0700 (PDT) [thread overview]
Message-ID: <20080529.034728.225207018.davem@davemloft.net> (raw)
In-Reply-To: <483DD775.2070901@candelatech.com>
From: Ben Greear <greearb@candelatech.com>
Date: Wed, 28 May 2008 15:06:45 -0700
> Now I wonder: If a reader read only a small bit of the proc file,
> and then just went to sleep w/out closing or reading the rest of
> the file, would that effectively DOS a system by pinning the locks?
That's not how this works.
The in-kernel buffer used by the SEQ file infrastructure is
filled as best as possible. Then the locks are dropped and
the copy to userspace is performed.
Since we hold locks, this also means preemption is disabled.
So there is no way for the task to go to sleep at this
time.
prev parent reply other threads:[~2008-05-29 10:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-28 21:38 Question on ipmr.c locking in 2.6.25 Ben Greear
2008-05-28 21:58 ` Ben Hutchings
2008-05-28 22:06 ` Ben Greear
2008-05-29 10:47 ` David Miller [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=20080529.034728.225207018.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bhutchings@solarflare.com \
--cc=greearb@candelatech.com \
--cc=netdev@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).