From: Christoph Rohland <cr@sap.com>
To: Dave Gilbert <gilbertd@treblig.org>
Cc: Linus Torvalds <torvalds@transmeta.com>, linux-kernel@vger.kernel.org
Subject: Re: [Patch] shmmin behaviour back to 2.2 behaviour
Date: 27 Dec 2000 16:37:15 +0100 [thread overview]
Message-ID: <m3r92tancw.fsf@linux.local> (raw)
In-Reply-To: <Pine.LNX.4.10.10012271156200.2753-100000@tardis.home.dave>
In-Reply-To: <Pine.LNX.4.10.10012271156200.2753-100000@tardis.home.dave>
Dave Gilbert <gilbertd@treblig.org> writes:
> I think I've come to the conclusion that Xine does not in the case
> I've found, rely on this - it is a separate bug related to Xv
> telling xine that it needs 0 bytes.
Yes, but this bug did not show on 2.2. It simply failed in shmget.
Probably it makes more sense to fail on creation of zero byte segments
and getting existing ones with zero length being legal... (The latter
is needed). That's what the patch does.
Greetings
Christoph
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-27 16:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-27 10:32 [Patch] shmmin behaviour back to 2.2 behaviour Christoph Rohland
2000-12-27 11:58 ` Dave Gilbert
2000-12-27 15:37 ` Christoph Rohland [this message]
2000-12-27 15:16 ` Marcelo Tosatti
2000-12-27 17:54 ` Christoph Rohland
2000-12-27 20:57 ` Andries Brouwer
2000-12-28 12:01 ` Christoph Rohland
2000-12-28 13:34 ` Andries Brouwer
2000-12-28 15:49 ` Alan Cox
2000-12-28 22:13 ` Christoph Rohland
2000-12-28 22:19 ` Alan Cox
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=m3r92tancw.fsf@linux.local \
--to=cr@sap.com \
--cc=gilbertd@treblig.org \
--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