Penchala Narasimha Reddy Chilakala, TLS-Chennai wrote:
> Hi James,
>
> Please let me know your opinion on the explanation given by me in the
> previous e-mail to the issue raised by you so that I will proceed
> further based on your feedback
[...]
> -----Original Message-----
> From: Penchala Narasimha Reddy Chilakala, TLS-Chennai
> Sent: Friday, October 23, 2009 6:41 PM
[...]
> Here is my explanation for the change. We have done good amount of
> review and testing before finalizing the change. We found the following
> code also caused to exit the management request prematurely without
> getting response from the firmware during our review, which in turn
> caused to generated False Raid Alert events in the application layer.
>
> So after doing good amount of review and testing, we replace the below
> code
>
> else if (down_interruptible(&fibptr->event_wait)) {
> fibptr->done = 2;
> up(&fibptr->event_wait);
> }
>
> With the following code
> } else
> down_interruptible (&fibptr->event_wait);
>
> To overcome the warning,
[i.e. "warning: ignoring return value of 'down_interruptible', declared
with attribute warn_unused_result"]
> we can replace the above code with either
>
> } else if (down_interruptible (&fibptr->event_wait));
>
> Or
>
> } else {
> if (down_interruptible (&fibptr->event_wait))
> ;
> }
>
> I am ok to do the above mentioned change in the code and resubmit the
> patch with the above change as there is no issue with respect to
> functionality and other aspects as such.
I'm not James, but I do have a suggestion:
Leave the compiler warning there for the short term. And then, instead
of suppressing the warning with hard to read code, convert from
semaphore to completion (or waitqueue perhaps).
I'm not familiar with aacraid but your problem description sounds to me
as if the legacy counting semaphore API is not the correct kernel API to
use here.
--
Stefan Richter
-=====-==--= =-=- ===--
http://arcgraph.de/sr/
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
