<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<small>Hi Michael,</small><br>
<br>
<div class="moz-cite-prefix">On 07/08/2015 04:12 PM, Michael
Ellerman wrote:<br>
</div>
<blockquote cite="mid:20150708104201.52B3D140AF3@ozlabs.org"
type="cite">
<pre wrap="">On Wed, 2015-08-07 at 06:27:28 UTC, Neelesh Gupta wrote:
</pre>
<blockquote type="cite">
<pre wrap="">If the OPAL call to receive the ipmi message fails, then we free up the smi
message before returning. But, the driver still holds the reference to old
smi message in the 'cur_msg' which is dangerous if the driver derefernces it
later and it will further block the subsequent ipmi operations.
</pre>
</blockquote>
<pre wrap="">
This doesn't sound like "a minor bug" ?
What are the actual symptoms of the bug? Does it crash, always, sometimes? Does
it actually "block the subsequent ipmi operations"?</pre>
</blockquote>
<br>
<small>In the normal scenario, it doesn't happen.<br>
To create the crash, I passed error code in opal call
'opal_ipmi_recv()'<br>
I think there is more need to be done than this change. So, I will
resend<br>
the next version addressing all of your concerns.<br>
<br>
Thanks,<br>
Neelesh.<br>
</small><br>
<blockquote cite="mid:20150708104201.52B3D140AF3@ozlabs.org"
type="cite">
<pre wrap="">
Even if this *is* a minor bug, please give it a proper subject that describes
what it does.
Also which commit introduced the bug?
And finally you don't seem to have CC'ed the ipmi maintainers?
cheers
</pre>
</blockquote>
<br>
</body>
</html>