From: Pete Zaitcev <zaitcev@redhat.com>
To: viro@math.psu.edu
Cc: linux-kernel@vger.kernel.org
Subject: path_release missing or not?
Date: Tue, 12 Nov 2002 17:11:10 -0500 [thread overview]
Message-ID: <20021112171110.A21229@devserv.devel.redhat.com> (raw)
Al, please tell me if the patch below is bogus. I checked paths
and it looks right, but I may be missing something.
-- Pete
--- linux-2.4.19/fs/namei.c 2002-08-02 17:39:45.000000000 -0700
+++ linux-2.4.19-p3/fs/namei.c 2002-11-12 14:01:55.000000000 -0800
@@ -1984,8 +1984,10 @@
* bloody create() on broken symlinks. Furrfu...
*/
name = __getname();
- if (!name)
+ if (!name) {
+ path_release(nd);
return -ENOMEM;
+ }
strcpy(name, nd->last.name);
nd->last.name = name;
return 0;
next reply other threads:[~2002-11-12 22:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-12 22:11 Pete Zaitcev [this message]
2002-11-12 22:28 ` Alexander Viro
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=20021112171110.A21229@devserv.devel.redhat.com \
--to=zaitcev@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.edu \
/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
all inboxes | Powered by JetHome®