You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to test some LIO Linux iSCSI target code, to see if my recently-proposed changes will break anything. In particular, I need to test that my target's handling of "Immediate Data" is broken.
I've done some manual testing, but I was wondering if there's anything in libiscsi that tests this specifically? I looked but wasn't sure about what I found ...
Thanks!
The text was updated successfully, but these errors were encountered:
On Tue, 9 Jan 2024 at 05:18, Lee Duncan ***@***.***> wrote:
Hi Ronnie! Long time no talk!
Long time indeed!
Not sure if there are any tests for immediate data explicitely.
Let me take some time over the weekend to have a look.
regards
ronnie sahlberg
I am trying to test some LIO Linux iSCSI target code, to see if my
recently-proposed changes will break anything. In particular, I need to
test that my target's handling of "Immediate Data" is broken.
I've done some manual testing, but I was wondering if there's anything in
libiscsi that tests this specifically? I looked but wasn't sure about what
I found ...
Thanks!
—
Reply to this email directly, view it on GitHub
<#407>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADY3EEB73XVRIGL4KNVQA3YNRA7LAVCNFSM6AAAAABBR6IOECVHI2DSMVQWIX3LMV43ASLTON2WKOZSGA3TCMBXGU4TINY>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
Hi Ronnie! Long time no talk!
I am trying to test some LIO Linux iSCSI target code, to see if my recently-proposed changes will break anything. In particular, I need to test that my target's handling of "Immediate Data" is broken.
I've done some manual testing, but I was wondering if there's anything in libiscsi that tests this specifically? I looked but wasn't sure about what I found ...
Thanks!
The text was updated successfully, but these errors were encountered: