<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED --- - set-to-domain returned EIO"
href="https://bugs.freedesktop.org/show_bug.cgi?id=74007#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED --- - set-to-domain returned EIO"
href="https://bugs.freedesktop.org/show_bug.cgi?id=74007">bug 74007</a>
from <span class="vcard"><a class="email" href="mailto:mika.kuoppala@intel.com" title="Mika Kuoppala <mika.kuoppala@intel.com>"> <span class="fn">Mika Kuoppala</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=74007#c4">comment #4</a>)
<span class="quote">> I still strongly believe that these interfaces (set-to-domain, pagefault)
> are special in that they require defense against internal errors. They are
> userspaces last resort at keeping the machine limping along long enough for
> people to save their work and report a bug.</span >
Ok. Do you consider also returning -EIO if the test has gone wild with
'stop_rings' debugfs interface to be an inssue ?
Another example:
Userspace sends hanging batch into multiple rings and then does set_domain().
Is -EIO acceptable in this case?</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>