From: "Anthony J. Battersby" <abatters@widomaker.com>
To: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: [PATCH] one-line bugfix 2.4.2 iobuf.c
Date: Mon, 26 Mar 2001 20:54:17 -0500 [thread overview]
Message-ID: <3ABFF2C9.96BE799B@widomaker.com> (raw)
Explanation:
The bufp pointer should be indexed rather than incremented because it is used
a few lines above as a base pointer to free successfully allocated items if
kmalloc fails.
-------- Begin Patch --------
--- fs/iobuf.c.orig Wed Mar 21 10:12:36 2001
+++ fs/iobuf.c Wed Mar 21 10:12:30 2001
@@ -55,7 +55,7 @@
return -ENOMEM;
}
kiobuf_init(iobuf);
- *bufp++ = iobuf;
+ bufp[i] = iobuf;
}
return 0;
-------- End Patch --------
When replying, please CC me at abatters@widomaker.com since I am not subscribed to
the mailing list.
--Tony Battersby
reply other threads:[~2001-03-27 1:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3ABFF2C9.96BE799B@widomaker.com \
--to=abatters@widomaker.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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