> On Thu, Jul 24, 2014 at 12:53:30PM -0700, Ben Pfaff wrote:
>> The umask is a process-wide value, so bind_unix_socket() races with file
>> creation in other Open vSwitch threads. This fixes the race.
>>
>> The workaround for non-Linux systems is not ideal, but I do not know any
>> other general
On Thu, Aug 07, 2014 at 02:31:24PM -0300, Flavio Leitner wrote:
> On Thu, Jul 24, 2014 at 12:53:30PM -0700, Ben Pfaff wrote:
> > The umask is a process-wide value, so bind_unix_socket() races with file
> > creation in other Open vSwitch threads. This fixes the race.
> >
> > The workaround for non
On Thu, Jul 24, 2014 at 12:53:30PM -0700, Ben Pfaff wrote:
> The umask is a process-wide value, so bind_unix_socket() races with file
> creation in other Open vSwitch threads. This fixes the race.
>
> The workaround for non-Linux systems is not ideal, but I do not know any
> other general solutio
On Thu, Jul 24, 2014 at 12:53:30PM -0700, Ben Pfaff wrote:
> The umask is a process-wide value, so bind_unix_socket() races with file
> creation in other Open vSwitch threads. This fixes the race.
>
> The workaround for non-Linux systems is not ideal, but I do not know any
> other general solutio
The umask is a process-wide value, so bind_unix_socket() races with file
creation in other Open vSwitch threads. This fixes the race.
The workaround for non-Linux systems is not ideal, but I do not know any
other general solution. I tested the workaround only on Linux.
CC: YAMAMOTO Takashi
Sig