From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: Disconnect <lkml@sigkill.net>, linux-kernel@vger.kernel.org
Subject: Re: [STUPID] Best looking code to transfer to a t-shirt
Date: Fri, 3 Jan 2003 14:53:38 -0200 [thread overview]
Message-ID: <20030103165337.GH20463@conectiva.com.br> (raw)
In-Reply-To: <Pine.LNX.4.33L2.0301030831190.32697-100000@dragon.pdx.osdl.net>
Em Fri, Jan 03, 2003 at 08:32:55AM -0800, Randy.Dunlap escreveu:
> | On Fri, 2003-01-03 at 08:25, Maciej Soltysiak wrote:
> | > Hi,
> | >
> | > I am in a t-shirt transfering frenzy and was wondering which part of the
> | > kernel code it would be best to have on my t-shirt.
> | > I was looking at my favourite: netfilter code, but it is to clean, short
> | > and simple functions, no tons of pointers, no mallocs, no hex numbers, too
> | > many defines used. I was looking for something terribly complicated and
> | > looking awesome to the eye.
> | >
> | > How about we have a poll of the most frightening pieces of the kernel ?
> | > What are your ideas?
>
> (not 'code')
> Take the ASCII art from the Sparc and PA-RISC die() functions, like so:
>
>
>
> die_on_sparc: die_on_parisc:
> _______________________________
> < Your System ate a SPARC! Gah! >
> \|/ ____ \|/ -------------------------------
> "@'/ .. \`@" \ ^__^
> /_| \__/ |_\ \ (xx)\_______
> \__U_/ (__)\ )\/\
> U ||----w |
> || ||
Hey, dont forget this one:
void ipgre_err(struct sk_buff *skb, u32 info)
{
#ifndef I_WISH_WORLD_WERE_PERFECT
/* It is not :-( All the routers (except for Linux) return only
8 bytes of packet payload. It means, that precise relaying of
ICMP in the real Internet is absolutely infeasible.
Moreover, Cisco "wise men" put GRE key to the third word
in GRE header. It makes impossible maintaining even soft state for keyed
GRE tunnels with enabled checksum. Tell them "thank you".
Well, I wonder, rfc1812 was written by Cisco employee,
what the hell these idiots break standrads established
by themself???
*/
struct iphdr *iph = (struct iphdr*)skb->data;
net/ipv4/ip_gre.c::317
8)
- Arnaldo
next prev parent reply other threads:[~2003-01-03 16:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-03 13:25 [STUPID] Best looking code to transfer to a t-shirt Maciej Soltysiak
2003-01-03 13:26 ` Jose Celestino
2003-01-03 14:55 ` Matthias Schniedermeyer
2003-01-03 15:03 ` Anders Gustafsson
2003-01-03 15:11 ` Tomas Szepe
2003-01-03 15:59 ` Disconnect
2003-01-03 16:32 ` Randy.Dunlap
2003-01-03 16:53 ` Arnaldo Carvalho de Melo [this message]
2003-01-03 16:33 ` Alvaro Lopes
2003-01-03 22:58 ` Rik van Riel
2003-01-03 23:39 ` William Lee Irwin III
2003-01-04 0:20 ` Ranjeet Shetye
2003-01-04 13:46 ` Maciej Soltysiak
2003-01-04 13:47 ` Maciej Soltysiak
2003-01-05 3:55 ` Randy.Dunlap
-- strict thread matches above, loose matches on Subject: below --
2003-01-03 14:53 uaca
2003-01-04 0:13 Nivedita Singhvi
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=20030103165337.GH20463@conectiva.com.br \
--to=acme@conectiva.com.br \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@sigkill.net \
--cc=rddunlap@osdl.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