From: Cort Dougan <cort@fsmlabs.com>
To: Alexander Viro <viro@math.psu.edu>
Cc: Erik Mouw <J.A.K.Mouw@its.tudelft.nl>,
Daniel Phillips <phillips@bonn-fries.net>,
Alan Cox <alan@lxorguk.ukuu.org.uk>, Val Henson <val@nmt.edu>,
"Randy.Dunlap" <rddunlap@osdl.org>, Laurent <laurent@augias.org>,
linux-kernel@vger.kernel.org
Subject: Re: read_proc issue
Date: Fri, 1 Mar 2002 12:49:07 -0700 [thread overview]
Message-ID: <20020301124907.H31407@host110.fsmlabs.com> (raw)
In-Reply-To: <20020301071410.GA11256@arthur.ubicom.tudelft.nl> <Pine.GSO.4.21.0203010245150.2886-100000@weyl.math.psu.edu>
In-Reply-To: <Pine.GSO.4.21.0203010245150.2886-100000@weyl.math.psu.edu>; from viro@math.psu.edu on Fri, Mar 01, 2002 at 02:47:26AM -0500
Yes, please kill it! seq files are much better and don't give people as
much of a chance to do things the wrong way. Fewer interfaces to /proc
would be vast improvement.
} Oh, for fsck sake...
}
} We already have better mechanism. Let ->proc_read() die, it's an ugly
} kludge, breeding overcomplicated code and buffer overflows.
}
} -
} To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
} the body of a message to majordomo@vger.kernel.org
} More majordomo info at http://vger.kernel.org/majordomo-info.html
} Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2002-03-01 19:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-26 18:21 read_proc issue Laurent
2002-02-27 19:33 ` Randy.Dunlap
2002-02-27 21:04 ` Val Henson
2002-02-27 21:42 ` Alan Cox
2002-02-27 21:44 ` Cort Dougan
2002-02-28 0:05 ` Erik Mouw
2002-02-27 3:19 ` Daniel Phillips
2002-03-01 7:14 ` Erik Mouw
2002-03-01 7:47 ` Alexander Viro
2002-03-01 8:18 ` Laurent
2002-03-01 8:18 ` Alexander Viro
2002-03-01 19:49 ` Cort Dougan [this message]
2002-02-27 23:32 ` Laurent
-- strict thread matches above, loose matches on Subject: below --
2002-02-27 0:51 Thomas Hood
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=20020301124907.H31407@host110.fsmlabs.com \
--to=cort@fsmlabs.com \
--cc=J.A.K.Mouw@its.tudelft.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=laurent@augias.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@bonn-fries.net \
--cc=rddunlap@osdl.org \
--cc=val@nmt.edu \
--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