From: Dave Jones <davej@redhat.com>
To: Neil Horman <nhorman@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Patch] add check to /proc/devices read routines
Date: Tue, 26 Apr 2005 21:20:03 -0400 [thread overview]
Message-ID: <20050427012003.GA31496@redhat.com> (raw)
In-Reply-To: <20050427010827.GA2451@hmsendeavour.rdu.redhat.com>
On Tue, Apr 26, 2005 at 09:08:27PM -0400, Neil Horman wrote:
> Patch to add check to get_chrdev_list and get_blkdev_list to prevent reads of
> /proc/devices from spilling over the provided page if more than 4096 bytes of
> string data are generated from all the registered character and block devices in
> a system
>
> Signed-off-by: Neil Horman <nhorman@redhat.com>
>
>
> fs/char_dev.c | 13 ++++++++++++-
> fs/proc/proc_misc.c | 2 +-
> include/linux/genhd.h | 2 +-
> 3 files changed, 14 insertions(+), 3 deletions(-)
Missing changes to drivers/block/genhd.c perhaps ?
You changed the prototype of get_blkdev_list(), but not
the implementation, which still takes a single arg.
I've not looked at this code at all, but it smells like
something that perhaps needs converting to use seq_file() and friends ?
Dave
next prev parent reply other threads:[~2005-04-27 1:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-27 1:08 [Patch] add check to /proc/devices read routines Neil Horman
2005-04-27 1:20 ` Dave Jones [this message]
2005-04-27 11:28 ` Neil Horman
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=20050427012003.GA31496@redhat.com \
--to=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nhorman@redhat.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