Re: exfat filesystem

2019-07-09 Thread Theodore Ts'o
On Tue, Jul 09, 2019 at 08:48:34AM -0700, Matthew Wilcox wrote: > > Interesting analysis. It seems to me that the correct forms would be > observed if someone suitably senior at Microsoft accepted the work from > Valdis and submitted it with their sign-off. KY, how about it? It might be that th

Re: Procedure questions - new filesystem driver..

2019-07-09 Thread Theodore Ts'o
On Tue, Jul 09, 2019 at 04:21:36AM -0700, Matthew Wilcox wrote: > How does > https://www.zdnet.com/article/microsoft-open-sources-its-entire-patent-portfolio/ > change your personal opinion? According to SFC's legal analysis, Microsoft joining the OIN doesn't mean that the eXFAT patents are covere

Re: Procedure questions - new filesystem driver..

2019-07-08 Thread Theodore Ts'o
On Mon, Jul 08, 2019 at 08:37:42PM -0400, Valdis Klētnieks wrote: > I have an out-of-tree driver for the exfat file system that I beaten into > shape > for upstreaming. The driver works, and passes sparse and checkpatch (except > for a number of line-too-long complaints). > > Do you want this tak

Re: Clarification for the use of additional fields in the message body

2015-07-09 Thread Theodore Ts'o
On Wed, Jul 08, 2015 at 05:27:38PM +0200, SF Markus Elfring wrote: > > Note also that some maintainers have work flow that deliberately smash > > the date (i.e., because they are using a system such as guilt), > > so if you are depending on the submitted timestamp, it's going to > > break on you. >

Re: Clarification for the use of additional fields in the message body

2015-07-08 Thread Theodore Ts'o
On Wed, Jul 08, 2015 at 09:05:53PM +1000, Julian Calaby wrote: > If multiple people are submitting identical changes, then the one that > is applied is the one the maintainer sees first, which will most > likely be determined by which one hit their inbox / list first. Nobody > is going to look at t

Re: lustre: why does cfs_get_random_bytes() exist?

2013-10-05 Thread Theodore Ts'o
On Sat, Oct 05, 2013 at 06:10:54AM +, Dilger, Andreas wrote: > >With modern kernels, the /dev/random driver has the > >add_device_randomness() interface which is used to mix in > >personalization information, which includes the network MAC address. > >So that particular concern should be covere

Re: lustre: why does cfs_get_random_bytes() exist?

2013-10-03 Thread Theodore Ts'o
On Thu, Oct 03, 2013 at 11:06:58PM +, Dilger, Andreas wrote: > > The Lustre cfs_get_random_bytes() incorporates (via cfs_rand()) a seed > which > also hashes in the addresses from any network interfaces that are > configured. > Conversely, cfs_rand() also is seeded at startup from get_random_b

Re: lustre: why does cfs_get_random_bytes() exist?

2013-10-03 Thread Theodore Ts'o
On Thu, Oct 03, 2013 at 10:26:21AM -0700, Greg KH wrote: > > Does this sound reasonable? > > Sounds reasonable to me, care to send a patch to do so? > I can do that, but I was waiting for Andras, Peng or Nikita to let me now if there was something I was missing or not. I'm pretty sure it's some

lustre: why does cfs_get_random_bytes() exist?

2013-10-03 Thread Theodore Ts'o
I've been auditing uses of get_random_bytes() since there are places where get_random_bytes() is getting used where something weaker, such as prandom_u32() is quite sufficient. Basically, if kernel code just needs a random number which does not have any cryptographic requirements (such as in ext[2