From: David Eger <eger@havoc.gtf.org>
To: viro@parcelfarce.linux.theplanet.co.uk
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: generic_readlink() - patch WFM
Date: Thu, 24 Jun 2004 18:41:21 -0400 [thread overview]
Message-ID: <20040624224120.GA12641@havoc.gtf.org> (raw)
In-Reply-To: <20040624212417.GG12308@parcelfarce.linux.theplanet.co.uk>
On Thu, Jun 24, 2004 at 10:24:17PM +0100, viro@parcelfarce.linux.theplanet.co.uk wrote:
> > I got this oops on boot with the latest Bitkeeper snapshot of 2.6.7
>
> Memory corruption in generic_readlink(), now that we use nd->depth instead
> of current->link_count. Fix follows:
what a nasty bug. your patch works for me.
prev parent reply other threads:[~2004-06-24 22:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-24 21:16 Oops with 2.6.7-bk Marcel Holtmann
2004-06-24 21:24 ` viro
2004-06-24 22:41 ` David Eger [this message]
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=20040624224120.GA12641@havoc.gtf.org \
--to=eger@havoc.gtf.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.