From: Frederic Weisbecker <fweisbec@gmail.com>
To: Matt Mackall <mpm@selenic.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH] random: Forbid llseek on random chardev
Date: Sat, 10 Apr 2010 18:35:30 +0200 [thread overview]
Message-ID: <20100410163529.GI5204@nowhere> (raw)
In-Reply-To: <1270916750.28124.23.camel@calx>
On Sat, Apr 10, 2010 at 11:25:50AM -0500, Matt Mackall wrote:
> On Sat, 2010-04-10 at 16:17 +0200, Frederic Weisbecker wrote:
> > From: Arnd Bergmann <arnd@arndb.de>
> >
> > Seeking on /dev/random and /dev/urandom is pointless.
>
> It is indeed pointless, though that doesn't mean no one does it.
> Forbidding a no-op seems a rather unfriendly way to fix this.
I worried about that too. If you think that could break some user
space apps, we can make it a generic_file_llseek.
> > Using generic_file_llseek means we no longer need to
> > take the BKL if anyone tries to seek on these.
>
> Comment doesn't match the patch?
Oops. I guess the patch has been updated, but not the changelog.
Some background: we are trying to remove the uses of default_llseek
that use the bkl. We started with turning llseek stubs to
generic_file_llseek (or non seekable open in some cases), but we are
hesitating now and think about actually turn all the stubs that
might need the bkl into default_llseek, and fallback to
generic_file_llseek for all other stubs.
Depending on what we do I'll resend you an updated version
of this patch with generic_file_llseek, or I will let the stub
as is.
Thanks.
next prev parent reply other threads:[~2010-04-10 16:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-10 14:17 [PATCH] random: Forbid llseek on random chardev Frederic Weisbecker
2010-04-10 16:25 ` Matt Mackall
2010-04-10 16:35 ` Frederic Weisbecker [this message]
2010-04-10 16:59 ` Matt Mackall
2010-04-10 17:55 ` Arnd Bergmann
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=20100410163529.GI5204@nowhere \
--to=fweisbec@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.