lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 6 Dec 2016 20:01:39 -0800 From: Santosh Shilimkar <santosh.shilimkar@...cle.com> To: netdev@...r.kernel.org, davem@...emloft.net Cc: linux-kernel@...r.kernel.org, santosh.shilimkar@...cle.com Subject: [net-next][PATCH v2 01/18] RDS: log the address on bind failure It's useful to know the IP address when RDS fails to bind a connection. Thus, adding it to the error message. Orabug: 21894138 Reviewed-by: Wei Lin Guay <wei.lin.guay@...cle.com> Signed-off-by: Santosh Shilimkar <santosh.shilimkar@...cle.com> --- net/rds/bind.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/net/rds/bind.c b/net/rds/bind.c index 095f6ce..3a915be 100644 --- a/net/rds/bind.c +++ b/net/rds/bind.c @@ -176,8 +176,8 @@ int rds_bind(struct socket *sock, struct sockaddr *uaddr, int addr_len) if (!trans) { ret = -EADDRNOTAVAIL; rds_remove_bound(rs); - printk_ratelimited(KERN_INFO "RDS: rds_bind() could not find a transport, " - "load rds_tcp or rds_rdma?\n"); + pr_info_ratelimited("RDS: %s could not find a transport for %pI4, load rds_tcp or rds_rdma?\n", + __func__, &sin->sin_addr.s_addr); goto out; } -- 1.9.1
Powered by blists - more mailing lists