On 09/26/2011 12:28 AM, Vivek S wrote: > On Mon, Sep 26, 2011 at 5:51 AM, Mike Christie <[email protected]> wrote: > >> On 09/25/2011 01:57 AM, Vivek S wrote: >>> >>> It's not working because the locking changed in that upstream kernel. >>> >>> >>> Hmm, okay. I will go back to a kernel that is supported by upstream >>> open-iscsi. >> >> I think you misunderstood me. With newer kernels you should just use the >> kernel modules in the kernel. You do not need the open-iscsi/kernel >> modules in those kernels. The upstream ones are good enough. > > > I was trying to dig into open-iscsi code and do some experiments with > session recovery. So I was using open-iscsi code from github. > > >> In the case of the stable kernels they are probably best to use since fixes >> that get >> sent upstream are sent to the stable kernels. >> > > That means I have to use stable kernels for open-iscsi development ? >
It depends on what you are working on. The userspace tools work with newer kernels (from 2.6.26 and newer) just fine. If you are just doing userspace work then you can use the open-iscsi tools from the github git tree (and kernel.org when it is back up) or open-iscsi.org tarballs with any of those kernels. If you are doing kernel work then it is best to be using the scsi maintainer's scsi-misc or scsi-rc-fixes tree or my linux-2.6.iscsi tree (I have not put up a new kernel tree because it is basically just scsi-misc right now and I have been hoping kernel.org would be back up soon). -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
