linux-kernel - Re: error to be returned while suspended

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 3 Oct 2006 10:17:59 -0400
From:	"linux-os \(Dick Johnson\)" <linux-os@...logic.com>
To:	"Oliver Neukum" <oliver@...kum.org>
Cc:	<linux-kernel@...r.kernel.org>
Subject: Re: error to be returned while suspended

On Tue, 3 Oct 2006, Oliver Neukum wrote:

> Am Dienstag, 3. Oktober 2006 14:51 schrieb linux-os (Dick Johnson):
>>
>> On Tue, 3 Oct 2006, Oliver Neukum wrote:
>>
>>> Hi,
>>>
>>> which error should a character device return if a read/write cannot be
>>> serviced because the device is suspended? Shouldn't there be an error
>>> code specific to that?
>>>
>>> 	Regards
>>> 		Oliver
>>
>> The de-facto error codes were created long before one could "suspend"
>> a device, so there isn't a ESUSP code. However, I suggest EIO or EBUSY
>
> CUPS chokes on these. Is it acceptable to say that you should know
> what you're doing when suspending?
>

Well, you need to look at the CUPS documentation and find out
what return code would be non-fatal and tell it to buffer stuff
to try later (such as the return code you get when the printer
if off-line).

 	http://www.cups.org/documentation.php

>> unless you want to define an ESUSP and get it accepted by the POSIX
>> committee.
>

Even if you did that, CUPS would have to be modified to accept
the new error code. There should be a current error code that
will allow CUPS to continue.

> This would be the cleanest solution. How does one do that?
>
> 	Regards
> 		Oliver
>

Cheers,
Dick Johnson
Penguin : Linux version 2.6.16.24 on an i686 machine (5592.72 BogoMips).
New book: http://www.AbominableFirebug.com/
_
..

****************************************************************
The information transmitted in this message is confidential and may be privileged.  Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited.  If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to DeliveryErrors@...logic.com - and destroy all copies of this information, including any attachments, without reading or disclosing them.

Thank you.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/