public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Halasa <khc@pm.waw.pl>
To: Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>
Cc: netdev@vger.kernel.org, David Miller <davem@davemloft.net>
Subject: Re: [PATCH] NET: fix kernel panic from no dev->hard_header_len space
Date: Fri, 28 Jul 2006 16:11:54 +0200	[thread overview]
Message-ID: <m3slklq0np.fsf@defiant.localdomain> (raw)
In-Reply-To: <m3ac6vx8ik.fsf@defiant.localdomain> (Krzysztof Halasa's message of "Thu, 27 Jul 2006 19:28:03 +0200")

Krzysztof Halasa <khc@pm.waw.pl> writes:

> Are you sure about that? It would mean almost devices, including
                                         ^^^^^^^^^^^^^^
> Ethernet, are at risk:

"almost all devices", of course.
-- 
Krzysztof Halasa

  reply	other threads:[~2006-07-28 14:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-27 13:56 [PATCH] NET: fix kernel panic from no dev->hard_header_len space Krzysztof Halasa
2006-07-27 16:43 ` Alexey Kuznetsov
2006-07-27 17:28   ` Krzysztof Halasa
2006-07-28 14:11     ` Krzysztof Halasa [this message]
2006-07-30 16:40   ` Krzysztof Halasa
2006-07-30 22:30     ` David Miller
2006-07-31 15:39       ` Alexey Kuznetsov
     [not found]         ` <m3r701zgku.fsf@defiant.localdomain>
2006-07-31 20:23           ` David Miller
2006-08-01  1:04             ` Krzysztof Halasa
2006-08-01  1:13               ` David Miller
2006-08-01  1:56                 ` Krzysztof Halasa
2006-08-01 19:54                   ` Alexey Kuznetsov
2006-08-02  0:24                     ` Krzysztof Halasa
2006-08-02  0:38                       ` David Miller
2006-08-02 21:11                         ` Krzysztof Halasa
2006-07-31 20:24           ` David Miller
2006-08-01 20:25     ` Alexey Kuznetsov
2006-08-02  0:42       ` Krzysztof Halasa
2006-08-02  0:48         ` David Miller

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=m3slklq0np.fsf@defiant.localdomain \
    --to=khc@pm.waw.pl \
    --cc=davem@davemloft.net \
    --cc=kuznet@ms2.inr.ac.ru \
    --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