Re: [PATCH net-next 4/9] rxrpc: Randomise epoch and starting client conn ID values

Reply inline On 9/5/2016 12:24 PM, David Howells wrote: > [cc'ing Jeff Altman for comment] > > David Laight wrote: > >>> Create a random epoch value rather than a time-based one on startup and set >>> the top bit to indicate that this is the case. >> >> Why set

Re: [PATCH net-next 4/9] rxrpc: Randomise epoch and starting client conn ID values

Reply inline On 9/5/2016 12:24 PM, David Howells wrote: > [cc'ing Jeff Altman for comment] > > David Laight wrote: > >>> Create a random epoch value rather than a time-based one on startup and set >>> the top bit to indicate that this is the case. >> >> Why set the top bit? >> There is

Re: [PATCH net-next 4/9] rxrpc: Randomise epoch and starting client conn ID values

[cc'ing Jeff Altman for comment] David Laight wrote: > > Create a random epoch value rather than a time-based one on startup and set > > the top bit to indicate that this is the case. > > Why set the top bit? > There is nothing to stop the time (in seconds) from having

Re: [PATCH net-next 4/9] rxrpc: Randomise epoch and starting client conn ID values

[cc'ing Jeff Altman for comment] David Laight wrote: > > Create a random epoch value rather than a time-based one on startup and set > > the top bit to indicate that this is the case. > > Why set the top bit? > There is nothing to stop the time (in seconds) from having the top bit set. >

RE: [PATCH net-next 4/9] rxrpc: Randomise epoch and starting client conn ID values

From: David Howells > Sent: 04 September 2016 22:03 > Create a random epoch value rather than a time-based one on startup and set > the top bit to indicate that this is the case. Why set the top bit? There is nothing to stop the time (in seconds) from having the top bit set. Nothing else can care

RE: [PATCH net-next 4/9] rxrpc: Randomise epoch and starting client conn ID values

From: David Howells > Sent: 04 September 2016 22:03 > Create a random epoch value rather than a time-based one on startup and set > the top bit to indicate that this is the case. Why set the top bit? There is nothing to stop the time (in seconds) from having the top bit set. Nothing else can care

[PATCH net-next 4/9] rxrpc: Randomise epoch and starting client conn ID values

Create a random epoch value rather than a time-based one on startup and set the top bit to indicate that this is the case. Also create a random starting client connection ID value. This will be incremented from here as new client connections are created. Signed-off-by: David Howells

[PATCH net-next 4/9] rxrpc: Randomise epoch and starting client conn ID values

Create a random epoch value rather than a time-based one on startup and set the top bit to indicate that this is the case. Also create a random starting client connection ID value. This will be incremented from here as new client connections are created. Signed-off-by: David Howells ---