Re: [PATCH 1/1] libiscsi regression in 2.6.25: fix setting of recv timer

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Bart Van Assche wrote:
On Fri, May 9, 2008 at 3:15 AM,  <michaelc@xxxxxxxxxxx> wrote:
From: Mike Christie <michaelc@xxxxxxxxxxx>

If the ping tmo is longer than the recv tmo then we could miss a window
where we were supposed to check the recv tmo. This happens because
the ping code will set the next timeout for the ping timeout, and if the
ping executes quickly there will be a long chunk of time before the
timer wakes up again.

This patch has the ping processing code kick off a recv
tmo check when getting a nop in response to our ping.

Signed-off-by: Mike Christie <michaelc@xxxxxxxxxxx>

Hello Mike,

Did you already consider to submit this patch for inclusion in a
2.6.25.x stable release ? See also
Documentation/stable_kernel_rules.txt for the details.


James does some magic where if we mark it as a regression against a previous kernel, when he merges it to send it upstream he will send cc the stable kernel guys for us. It is pretty neat like some sort of JamesBot :)
--
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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [SCSI Target Devel]     [Linux SCSI Target Infrastructure]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Samba]     [Device Mapper]
  Powered by Linux