netdev
[Top] [All Lists]

Re: [PATCH] NETLINK_UESTABLISHED notifier event

To: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [PATCH] NETLINK_UESTABLISHED notifier event
From: Dmitry Yusupov <dmitry_yus@xxxxxxxxx>
Date: Wed, 06 Apr 2005 14:37:21 -0700
Cc: Mike Christie <michaelc@xxxxxxxxxxx>, netdev@xxxxxxxxxxx, davem@xxxxxxxxxxxxx
In-reply-to: <20050406212906.GA24775@xxxxxxxxxxxxxxxxxxx>
References: <E1DJ0YI-0003PR-00@xxxxxxxxxxxxxxxxxxxxxxxx> <42540CF3.7070501@xxxxxxxxxxx> <20050406212906.GA24775@xxxxxxxxxxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
On Thu, 2005-04-07 at 07:29 +1000, Herbert Xu wrote:
> On Wed, Apr 06, 2005 at 09:23:15AM -0700, Mike Christie wrote:
> > 
> > It is due to where it is being used. open-iscsi uses netlink
> > sockets for communication in a block (scsi specificically)
> > driver that has pushed much of its code to usersapce. Forcing
> > open-iscsi to use GFP_KERNEL causes a couple of problems. The
> > worst would be where a GFP_KERNEL allocation causes a write,
> > and that write is to an iscsi disk that open-iscsi is managing.
> > The write could then hit the same code path and cause another
> > GFP_KERNEL allocation and we could loop like that until the
> > system locks up.
> 
> In that case it's not enough to just use sk_allocation here.
> You'll need a way to actually set it to GFP_ATOMIC.

correct.

That's why in my patch I provided NETLINK_UESTABLISHED event. It is a
right way and time to set sk->sk_allocation to GFP_ATOMIC for newly
established netlink connection. imho.


<Prev in Thread] Current Thread [Next in Thread>