linux-kernel - setsockopt

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Wed, 26 Jul 2006 12:36:29 +0530
From:	Chinmaya Mishra <chinmaya4@...il.com>
To:	undisclosed-recipients:;
Subject: setsockopt -  SO_REUSEADDR

Hi all,

I am creating a socket in kernel. It is able to bind. But after abnormal
termination of the module, I am not able to bind the socket once again. 
Here i use

.......................................................................
/* create a socket */
if ((err = sock_create(AF_INET, SOCK_DGRAM, IPPROTO_UDP, &sock)) < 0) {
    printk(KERN_INFO MODULE_NAME": Could not create a datagram socket, 
error = %d\n", -ENXIO);
    return;
}

if((err = sock->ops->setsockopt(sock, SOL_SOCKET, SO_REUSEADDR, 
(void*)&option, sizeof(option)))<0)
             printk(KERN_INFO MODULE_NAME": Error in set socket opt for 
SO_REUSEADDR \n");

memset(&addr, 0, sizeof(struct sockaddr));
addr.sin_family = AF_INET;
addr.sin_addr.s_addr = htonl(INADDR_ANY);
addr.sin_port = htons(7006);

if ((err = sock->ops->bind(sock, (struct sockaddr *)&addr, sizeof(struct 
sockaddr)))< 0)
{
    printk(KERN_INFO MODULE_NAME": Could not bind to socket, error = 
%d\n", -err);
    goto close_and_out;
}
 printk(KERN_INFO MODULE_NAME": listening on port %d\n", 7006);
...................................................................

It throwing the following error
    Error in set socket opt for SO_REUSEADDR
    Could not bind to socket, error = 98

Can you tell me what i am missing. Just I want to reuse the bind same 
address once again in the
same port.

Thanks.
Chinmaya
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/