iscsi-target: Put length of failed allocation in error message
If the message "Unable to allocate…" pops up, it's useful to know whether the problem is that the system is genuinely out of memory, or that some bug has led to a crazy allocation length. In particular this helped debug a corruption of login headers in iscsi_login_non_zero_tsih_s1(). Signed-off-by: Roland Dreier <roland@purestorage.com> Signed-off-by: Nicholas Bellinger <nab@linux-iscsi.org>
This commit is contained in:
parent
91f0abfda1
commit
cee6029ecf
|
@ -1605,7 +1605,7 @@ int iscsi_decode_text_input(
|
|||
|
||||
tmpbuf = kzalloc(length + 1, GFP_KERNEL);
|
||||
if (!tmpbuf) {
|
||||
pr_err("Unable to allocate memory for tmpbuf.\n");
|
||||
pr_err("Unable to allocate %u + 1 bytes for tmpbuf.\n", length);
|
||||
return -1;
|
||||
}
|
||||
|
||||
|
|
Loading…
Reference in New Issue