From: David Swasey <swasey@cs.cmu.edu>
To: 9fans@cse.psu.edu
Subject: [9fans] u9fs bug
Date: Fri, 23 May 2003 11:51:55 -0400 [thread overview]
Message-ID: <910d40a791450c3c2eb43cc7c99ba7e0@cs.cmu.edu> (raw)
In u9fs.c, gid2user() may return nil but groupchange() assumes g is
always non-nil. This causes u9fs to seg fault when, for example,
creating a file in a directory that has a group id not defined in
/etc/group. A simple fix is to have groupchange() handle the case
when g is nil:
/sys/src/cmd/unix/u9fs/u9fs.c:1320 a u9fs.c:1321,1322
> if(g == nil)
> return -1;
-dave
reply other threads:[~2003-05-23 15:51 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=910d40a791450c3c2eb43cc7c99ba7e0@cs.cmu.edu \
--to=swasey@cs.cmu.edu \
--cc=9fans@cse.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;
as well as URLs for NNTP newsgroup(s).