From: Andrew Friedley <saai@swbell.net>
To: "David S. Miller" <davem@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PPPOE can kfree SKB twice (was Re: kernel panic problem. (smp, iptables?))
Date: Thu, 19 Jul 2001 18:53:21 -0500 [thread overview]
Message-ID: <003d01c110ad$fe41db40$0200a8c0@loki> (raw)
In-Reply-To: <005f01c10e69$28273e60$0200a8c0@loki> <15189.2408.59953.395204@pizda.ninka.net> <sb6r8vcg31q.fsf@slug.watson.ibm.com> <15191.27007.837441.266822@pizda.ninka.net>
Hey, I'm having trouble applying your first patch to kernel 2.4.6. I have a
list of 18 failed hunks.
The command I used is: cd /usr/src/linux && patch -Np0 -i
/home/arch/pppoe-davidmiller.patch Is the patch for a different kernel? I
had the same problem applying it to 2.4.7-pre8.
Andrew Friedley
> Michal Ostrowski writes:
> > Alexey replied to my last post with some valuable comments and in
> > response I have a new patch (that goes on top of David Miller's patch
> > from yesterday).
>
> Applied to my tree, thanks.
>
> Later,
> David S. Miller
> davem@redhat.com
next prev parent reply other threads:[~2001-07-19 23:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-17 2:35 kernel panic problem. (smp, iptables?) Andrew Friedley
2001-07-18 3:58 ` [PATCH] PPPOE can kfree SKB twice (was Re: kernel panic problem. (smp, iptables?)) David S. Miller
2001-07-18 14:23 ` Michal Ostrowski
2001-07-19 12:30 ` Michal Ostrowski
2001-07-19 17:27 ` kuznet
2001-07-19 18:00 ` Michal Ostrowski
2001-07-19 18:17 ` kuznet
2001-07-19 18:57 ` Michal Ostrowski
2001-07-19 23:13 ` David S. Miller
2001-07-19 23:53 ` Andrew Friedley [this message]
2001-07-20 7:13 ` Rainer Clasen
2001-07-20 7:28 ` David S. Miller
2001-07-20 15:36 ` Rainer Clasen
2001-07-09 11:51 ` [OOPS] network related crash with Linux 2.4 Moritz Schulte
2001-07-10 5:19 ` Rainer Clasen
2001-08-01 20:21 ` Rainer Clasen
2001-07-22 2:07 ` kernel panic problem. (smp, iptables?) Rusty Russell
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='003d01c110ad$fe41db40$0200a8c0@loki' \
--to=saai@swbell.net \
--cc=davem@redhat.com \
--cc=linux-kernel@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