From: Jason Gunthorpe <jgg@ziepe.ca>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: linux-kernel@vger.kernel.org,
brcm80211-dev-list.pdl@broadcom.com, cake@lists.bufferbloat.net,
ceph-devel@vger.kernel.org, coreteam@netfilter.org,
dccp@vger.kernel.org, dev@openvswitch.org,
dmaengine@vger.kernel.org, drbd-dev@lists.linbit.com,
dri-devel@lists.freedesktop.org, kasan-dev@googlegroups.com,
linux-actions@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-block@vger.kernel.org, linux-crypto@vger.kernel.org,
linux-doc@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-fbdev@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-hams@vger.kernel.org, linux-media@vger.kernel.org,
linux-mm@kvack.org, linux-mmc@vger.kernel.org,
linux-mtd@lists.infradead.org, linux-nfs@vger.kernel.org,
linux-nvme@lists.infradead.org, linux-raid@vger.kernel.org,
linux-rdma@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-sctp@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-usb@vger.kernel.org, linux-wireless@vger.kernel.org,
linux-xfs@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
lvs-devel@vger.kernel.org, netdev@vger.kernel.org,
netfilter-devel@vger.kernel.org, rds-devel@oss.oracle.com,
SHA-cyfmac-dev-list@infineon.com, target-devel@vger.kernel.org,
tipc-discussion@lists.sourceforge.net
Subject: Re: [PATCH v1 3/5] treewide: use get_random_u32() when possible
Date: Thu, 6 Oct 2022 10:15:35 -0300 [thread overview]
Message-ID: <Yz7U99PPl8uHCLFY@ziepe.ca> (raw)
In-Reply-To: <CAHmME9r_vNRFFjUvqx8QkBddg_kQU=FMgpk9TqOVZdvX6zXHNg@mail.gmail.com>
On Thu, Oct 06, 2022 at 07:05:48AM -0600, Jason A. Donenfeld wrote:
> > > diff --git a/drivers/infiniband/ulp/ipoib/ipoib_cm.c b/drivers/infiniband/ulp/ipoib/ipoib_cm.c
> > > index fd9d7f2c4d64..a605cf66b83e 100644
> > > --- a/drivers/infiniband/ulp/ipoib/ipoib_cm.c
> > > +++ b/drivers/infiniband/ulp/ipoib/ipoib_cm.c
> > > @@ -465,7 +465,7 @@ static int ipoib_cm_req_handler(struct ib_cm_id *cm_id,
> > > goto err_qp;
> > > }
> > >
> > > - psn = prandom_u32() & 0xffffff;
> > > + psn = get_random_u32() & 0xffffff;
> >
> > prandom_max(0xffffff + 1)
>
> That'd work, but again it's not more clear. Authors here are going for
> a 24-bit number, and masking seems like a clear way to express that.
vs just asking directly for a 24 bit number?
Jason
WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@ziepe.ca>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: linux-fbdev@vger.kernel.org, linux-doc@vger.kernel.org,
linux-wireless@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-mm@kvack.org, linux-sctp@vger.kernel.org,
target-devel@vger.kernel.org, linux-mtd@lists.infradead.org,
linux-stm32@st-md-mailman.stormreply.com,
drbd-dev@lists.linbit.com, dev@openvswitch.org,
rds-devel@oss.oracle.com, linux-scsi@vger.kernel.org,
dccp@vger.kernel.org, linux-rdma@vger.kernel.org,
kasan-dev@googlegroups.com, lvs-devel@vger.kernel.org,
SHA-cyfmac-dev-list@infineon.com, coreteam@netfilter.org,
tipc-discussion@lists.sourceforge.net,
linux-ext4@vger.kernel.org, linux-media@vger.kernel.org,
linux-actions@lists.infradead.org, linux-nfs@vger.kernel.org,
linux-block@vger.kernel.org, dmaengine@vger.kernel.org,
linux-nvme@lists.infradead.org, linux-hams@vger.kernel.org,
ceph-devel@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
cake@lists.bufferbloat.net, brcm80211-dev-list.pdl@broadcom.com,
linux-raid@vger.kernel.org, netdev@vger.kernel.org,
linux-usb@vger.kernel.org, linux-mmc@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-xfs@vger.kernel.org, netfilter-devel@vger.kernel.org,
linux-crypto@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [f2fs-dev] [PATCH v1 3/5] treewide: use get_random_u32() when possible
Date: Thu, 6 Oct 2022 10:15:35 -0300 [thread overview]
Message-ID: <Yz7U99PPl8uHCLFY@ziepe.ca> (raw)
In-Reply-To: <CAHmME9r_vNRFFjUvqx8QkBddg_kQU=FMgpk9TqOVZdvX6zXHNg@mail.gmail.com>
On Thu, Oct 06, 2022 at 07:05:48AM -0600, Jason A. Donenfeld wrote:
> > > diff --git a/drivers/infiniband/ulp/ipoib/ipoib_cm.c b/drivers/infiniband/ulp/ipoib/ipoib_cm.c
> > > index fd9d7f2c4d64..a605cf66b83e 100644
> > > --- a/drivers/infiniband/ulp/ipoib/ipoib_cm.c
> > > +++ b/drivers/infiniband/ulp/ipoib/ipoib_cm.c
> > > @@ -465,7 +465,7 @@ static int ipoib_cm_req_handler(struct ib_cm_id *cm_id,
> > > goto err_qp;
> > > }
> > >
> > > - psn = prandom_u32() & 0xffffff;
> > > + psn = get_random_u32() & 0xffffff;
> >
> > prandom_max(0xffffff + 1)
>
> That'd work, but again it's not more clear. Authors here are going for
> a 24-bit number, and masking seems like a clear way to express that.
vs just asking directly for a 24 bit number?
Jason
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@ziepe.ca>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: linux-fbdev@vger.kernel.org, linux-doc@vger.kernel.org,
linux-wireless@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-mm@kvack.org, linux-sctp@vger.kernel.org,
target-devel@vger.kernel.org, linux-mtd@lists.infradead.org,
linux-stm32@st-md-mailman.stormreply.com,
drbd-dev@lists.linbit.com, dev@openvswitch.org,
rds-devel@oss.oracle.com, linux-scsi@vger.kernel.org,
dccp@vger.kernel.org, linux-rdma@vger.kernel.org,
kasan-dev@googlegroups.com, lvs-devel@vger.kernel.org,
SHA-cyfmac-dev-list@infineon.com, coreteam@netfilter.org,
tipc-discussion@lists.sourceforge.net,
linux-ext4@vger.kernel.org, linux-media@vger.kernel.org,
linux-actions@lists.infradead.org, linux-nfs@vger.kernel.org,
linux-block@vger.kernel.org, dmaengine@vger.kernel.org,
linux-nvme@lists.infradead.org, linux-hams@vger.kernel.org,
ceph-devel@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
cake@lists.bufferbloat.net, brcm80211-dev-list.pdl@broadcom.com,
linux-raid@vger.kernel.org, netdev@vger.kernel.org,
linux-usb@vger.kernel.org, linux-mmc@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-xfs@vger.kernel.org, netfilter-devel@vger.kernel.org,
linux-crypto@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v1 3/5] treewide: use get_random_u32() when possible
Date: Thu, 6 Oct 2022 10:15:35 -0300 [thread overview]
Message-ID: <Yz7U99PPl8uHCLFY@ziepe.ca> (raw)
In-Reply-To: <CAHmME9r_vNRFFjUvqx8QkBddg_kQU=FMgpk9TqOVZdvX6zXHNg@mail.gmail.com>
On Thu, Oct 06, 2022 at 07:05:48AM -0600, Jason A. Donenfeld wrote:
> > > diff --git a/drivers/infiniband/ulp/ipoib/ipoib_cm.c b/drivers/infiniband/ulp/ipoib/ipoib_cm.c
> > > index fd9d7f2c4d64..a605cf66b83e 100644
> > > --- a/drivers/infiniband/ulp/ipoib/ipoib_cm.c
> > > +++ b/drivers/infiniband/ulp/ipoib/ipoib_cm.c
> > > @@ -465,7 +465,7 @@ static int ipoib_cm_req_handler(struct ib_cm_id *cm_id,
> > > goto err_qp;
> > > }
> > >
> > > - psn = prandom_u32() & 0xffffff;
> > > + psn = get_random_u32() & 0xffffff;
> >
> > prandom_max(0xffffff + 1)
>
> That'd work, but again it's not more clear. Authors here are going for
> a 24-bit number, and masking seems like a clear way to express that.
vs just asking directly for a 24 bit number?
Jason
WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@ziepe.ca>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: linux-kernel@vger.kernel.org,
brcm80211-dev-list.pdl@broadcom.com, cake@lists.bufferbloat.net,
ceph-devel@vger.kernel.org, coreteam@netfilter.org,
dccp@vger.kernel.org, dev@openvswitch.org,
dmaengine@vger.kernel.org, drbd-dev@lists.linbit.com,
dri-devel@lists.freedesktop.org, kasan-dev@googlegroups.com,
linux-actions@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-block@vger.kernel.org, linux-crypto@vger.kernel.org,
linux-doc@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-fbdev@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-hams@vger.kernel.org, linux-media@vger.kernel.org,
linux-mm@kvack.org, linux-mmc@vger.kernel.org,
linux-mtd@lists.infradead.org, linux-nfs@vger.kernel.org,
linux-nvme@lists.infradead.org, linux-raid@vger.kernel.org,
linux-rdma@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-sctp@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-usb@vger.kernel.org, linux-wireless@vger.kernel.org,
linux-xfs@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
lvs-devel@vger.kernel.org, netdev@vger.kernel.org,
netfilter-devel@vger.kernel.org, rds-devel@oss.oracle.com,
SHA-cyfmac-dev-list@infineon.com, target-devel@vger.kernel.org,
tipc-discussion@lists.sourceforge.net
Subject: Re: [PATCH v1 3/5] treewide: use get_random_u32() when possible
Date: Thu, 6 Oct 2022 10:15:35 -0300 [thread overview]
Message-ID: <Yz7U99PPl8uHCLFY@ziepe.ca> (raw)
In-Reply-To: <CAHmME9r_vNRFFjUvqx8QkBddg_kQU=FMgpk9TqOVZdvX6zXHNg@mail.gmail.com>
On Thu, Oct 06, 2022 at 07:05:48AM -0600, Jason A. Donenfeld wrote:
> > > diff --git a/drivers/infiniband/ulp/ipoib/ipoib_cm.c b/drivers/infiniband/ulp/ipoib/ipoib_cm.c
> > > index fd9d7f2c4d64..a605cf66b83e 100644
> > > --- a/drivers/infiniband/ulp/ipoib/ipoib_cm.c
> > > +++ b/drivers/infiniband/ulp/ipoib/ipoib_cm.c
> > > @@ -465,7 +465,7 @@ static int ipoib_cm_req_handler(struct ib_cm_id *cm_id,
> > > goto err_qp;
> > > }
> > >
> > > - psn = prandom_u32() & 0xffffff;
> > > + psn = get_random_u32() & 0xffffff;
> >
> > prandom_max(0xffffff + 1)
>
> That'd work, but again it's not more clear. Authors here are going for
> a 24-bit number, and masking seems like a clear way to express that.
vs just asking directly for a 24 bit number?
Jason
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@ziepe.ca>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: linux-kernel@vger.kernel.org,
brcm80211-dev-list.pdl@broadcom.com, cake@lists.bufferbloat.net,
ceph-devel@vger.kernel.org, coreteam@netfilter.org,
dccp@vger.kernel.org, dev@openvswitch.org,
dmaengine@vger.kernel.org, drbd-dev@lists.linbit.com,
dri-devel@lists.freedesktop.org, kasan-dev@googlegroups.com,
linux-actions@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-block@vger.kernel.org, linux-crypto@vger.kernel.org,
linux-doc@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-fbdev@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-hams@vger.kernel.org, linux-media@vger.kernel.org,
linux-mm@kvack.org, linux-mmc@vger.kernel.org,
linux-mtd@lists.infradead.org, linux-nfs@vger.kernel.org,
linux-nvme@lists.infradead.org, linux-raid@vger.kernel.org,
linux-rdma@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-sctp@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-usb@vger.kernel.org, linux-wireless@vger.kernel.org,
linux-xfs@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
lvs-devel@vger.kernel.org, netdev@vger.kernel.org,
netfilter-devel@vger.kernel.org, rds-devel@oss.oracle.com,
SHA-cyfmac-dev-list@infineon.com, target-devel@vger.kernel.org,
tipc-discussion@lists.sourceforge.net
Subject: Re: [PATCH v1 3/5] treewide: use get_random_u32() when possible
Date: Thu, 6 Oct 2022 10:15:35 -0300 [thread overview]
Message-ID: <Yz7U99PPl8uHCLFY@ziepe.ca> (raw)
In-Reply-To: <CAHmME9r_vNRFFjUvqx8QkBddg_kQU=FMgpk9TqOVZdvX6zXHNg@mail.gmail.com>
On Thu, Oct 06, 2022 at 07:05:48AM -0600, Jason A. Donenfeld wrote:
> > > diff --git a/drivers/infiniband/ulp/ipoib/ipoib_cm.c b/drivers/infiniband/ulp/ipoib/ipoib_cm.c
> > > index fd9d7f2c4d64..a605cf66b83e 100644
> > > --- a/drivers/infiniband/ulp/ipoib/ipoib_cm.c
> > > +++ b/drivers/infiniband/ulp/ipoib/ipoib_cm.c
> > > @@ -465,7 +465,7 @@ static int ipoib_cm_req_handler(struct ib_cm_id *cm_id,
> > > goto err_qp;
> > > }
> > >
> > > - psn = prandom_u32() & 0xffffff;
> > > + psn = get_random_u32() & 0xffffff;
> >
> > prandom_max(0xffffff + 1)
>
> That'd work, but again it's not more clear. Authors here are going for
> a 24-bit number, and masking seems like a clear way to express that.
vs just asking directly for a 24 bit number?
Jason
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@ziepe.ca>
To: dccp@vger.kernel.org
Subject: Re: [PATCH v1 3/5] treewide: use get_random_u32() when possible
Date: Thu, 06 Oct 2022 13:15:35 +0000 [thread overview]
Message-ID: <Yz7U99PPl8uHCLFY@ziepe.ca> (raw)
In-Reply-To: <Yz7Rl7BXamKQhRzH@smile.fi.intel.com>
On Thu, Oct 06, 2022 at 07:05:48AM -0600, Jason A. Donenfeld wrote:
> > > diff --git a/drivers/infiniband/ulp/ipoib/ipoib_cm.c b/drivers/infiniband/ulp/ipoib/ipoib_cm.c
> > > index fd9d7f2c4d64..a605cf66b83e 100644
> > > --- a/drivers/infiniband/ulp/ipoib/ipoib_cm.c
> > > +++ b/drivers/infiniband/ulp/ipoib/ipoib_cm.c
> > > @@ -465,7 +465,7 @@ static int ipoib_cm_req_handler(struct ib_cm_id *cm_id,
> > > goto err_qp;
> > > }
> > >
> > > - psn = prandom_u32() & 0xffffff;
> > > + psn = get_random_u32() & 0xffffff;
> >
> > prandom_max(0xffffff + 1)
>
> That'd work, but again it's not more clear. Authors here are going for
> a 24-bit number, and masking seems like a clear way to express that.
vs just asking directly for a 24 bit number?
Jason
WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@ziepe.ca>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: linux-kernel@vger.kernel.org,
brcm80211-dev-list.pdl@broadcom.com, cake@lists.bufferbloat.net,
ceph-devel@vger.kernel.org, coreteam@netfilter.org,
dccp@vger.kernel.org, dev@openvswitch.org,
dmaengine@vger.kernel.org, drbd-dev@lists.linbit.com,
dri-devel@lists.freedesktop.org, kasan-dev@googlegroups.com,
linux-actions@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-block@vger.kernel.org, linux-crypto@vger.kernel.org,
linux-doc@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-fbdev@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-hams@vger.kernel.org, linux-media@vger.kernel.org,
linux-mm@kvack.org, linux-mmc@vger.kernel.org,
linux-mtd@lists.infradead.org, linux-nfs@vger.kernel.org,
linux-nvme@lists.infradead.org, linux-
Subject: Re: [PATCH v1 3/5] treewide: use get_random_u32() when possible
Date: Thu, 6 Oct 2022 10:15:35 -0300 [thread overview]
Message-ID: <Yz7U99PPl8uHCLFY@ziepe.ca> (raw)
In-Reply-To: <CAHmME9r_vNRFFjUvqx8QkBddg_kQU=FMgpk9TqOVZdvX6zXHNg@mail.gmail.com>
On Thu, Oct 06, 2022 at 07:05:48AM -0600, Jason A. Donenfeld wrote:
> > > diff --git a/drivers/infiniband/ulp/ipoib/ipoib_cm.c b/drivers/infiniband/ulp/ipoib/ipoib_cm.c
> > > index fd9d7f2c4d64..a605cf66b83e 100644
> > > --- a/drivers/infiniband/ulp/ipoib/ipoib_cm.c
> > > +++ b/drivers/infiniband/ulp/ipoib/ipoib_cm.c
> > > @@ -465,7 +465,7 @@ static int ipoib_cm_req_handler(struct ib_cm_id *cm_id,
> > > goto err_qp;
> > > }
> > >
> > > - psn = prandom_u32() & 0xffffff;
> > > + psn = get_random_u32() & 0xffffff;
> >
> > prandom_max(0xffffff + 1)
>
> That'd work, but again it's not more clear. Authors here are going for
> a 24-bit number, and masking seems like a clear way to express that.
vs just asking directly for a 24 bit number?
Jason
next prev parent reply other threads:[~2022-10-06 13:15 UTC|newest]
Thread overview: 207+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 21:48 [f2fs-dev] [PATCH v1 0/5] treewide cleanup of random integer usage Jason A. Donenfeld via Linux-f2fs-devel
2022-10-05 21:48 ` Jason A. Donenfeld via dev
2022-10-05 21:48 ` Jason A. Donenfeld
2022-10-05 21:48 ` Jason A. Donenfeld
2022-10-05 21:48 ` Jason A. Donenfeld
2022-10-05 21:48 ` Jason A. Donenfeld
2022-10-05 21:48 ` Jason A. Donenfeld
2022-10-05 21:48 ` [f2fs-dev] [PATCH v1 1/5] treewide: use prandom_u32_max() when possible Jason A. Donenfeld via Linux-f2fs-devel
2022-10-05 21:48 ` Jason A. Donenfeld via Linux-f2fs-devel
2022-10-05 21:48 ` Jason A. Donenfeld
2022-10-05 21:48 ` Jason A. Donenfeld
2022-10-05 21:48 ` Jason A. Donenfeld
2022-10-05 21:48 ` Jason A. Donenfeld
2022-10-05 21:48 ` Jason A. Donenfeld
2022-10-06 4:16 ` Kees Cook
2022-10-06 4:16 ` Kees Cook
2022-10-06 4:16 ` Kees Cook
2022-10-06 4:16 ` Kees Cook
2022-10-06 4:16 ` Kees Cook
2022-10-06 4:16 ` [f2fs-dev] " Kees Cook
2022-10-06 4:22 ` KP Singh
2022-10-06 4:22 ` KP Singh
2022-10-06 4:22 ` KP Singh
2022-10-06 4:22 ` KP Singh
2022-10-06 4:22 ` KP Singh
2022-10-06 4:22 ` KP Singh
2022-10-06 12:45 ` [f2fs-dev] " Jason A. Donenfeld via Linux-f2fs-devel
2022-10-06 12:45 ` Jason A. Donenfeld via dev
2022-10-06 12:45 ` Jason A. Donenfeld
2022-10-06 12:45 ` Jason A. Donenfeld
2022-10-06 12:45 ` Jason A. Donenfeld
2022-10-06 12:45 ` Jason A. Donenfeld
2022-10-06 12:55 ` Jason Gunthorpe
2022-10-06 12:55 ` Jason Gunthorpe
2022-10-06 12:55 ` Jason Gunthorpe
2022-10-06 12:55 ` Jason Gunthorpe
2022-10-06 12:55 ` Jason Gunthorpe
2022-10-06 12:55 ` [f2fs-dev] " Jason Gunthorpe
2022-10-06 13:05 ` Andy Shevchenko
2022-10-06 13:05 ` Andy Shevchenko
2022-10-06 13:05 ` Andy Shevchenko
2022-10-06 13:05 ` Andy Shevchenko
2022-10-06 13:05 ` Andy Shevchenko
2022-10-06 13:05 ` Andy Shevchenko
2022-10-06 9:07 ` Christoph Böhmwalder
2022-10-05 21:48 ` [f2fs-dev] [PATCH v1 2/5] treewide: use get_random_{u8, u16}() " Jason A. Donenfeld via Linux-f2fs-devel
2022-10-05 21:48 ` Jason A. Donenfeld via dev
2022-10-05 21:48 ` [PATCH v1 2/5] treewide: use get_random_{u8,u16}() " Jason A. Donenfeld
2022-10-05 21:48 ` Jason A. Donenfeld
2022-10-05 21:48 ` Jason A. Donenfeld
2022-10-05 21:48 ` Jason A. Donenfeld
2022-10-05 21:48 ` Jason A. Donenfeld
2022-10-06 4:38 ` Kees Cook
2022-10-06 4:38 ` [PATCH v1 2/5] treewide: use get_random_{u8, u16}() " Kees Cook
2022-10-06 4:38 ` [PATCH v1 2/5] treewide: use get_random_{u8,u16}() " Kees Cook
2022-10-06 4:38 ` Kees Cook
2022-10-06 4:38 ` Kees Cook
2022-10-06 4:38 ` [f2fs-dev] [PATCH v1 2/5] treewide: use get_random_{u8, u16}() " Kees Cook
2022-10-06 12:28 ` Jason A. Donenfeld via Linux-f2fs-devel
2022-10-06 12:28 ` Jason A. Donenfeld via dev
2022-10-06 12:28 ` [PATCH v1 2/5] treewide: use get_random_{u8,u16}() " Jason A. Donenfeld
2022-10-06 12:28 ` Jason A. Donenfeld
2022-10-06 12:28 ` Jason A. Donenfeld
2022-10-06 12:28 ` Jason A. Donenfeld
2022-10-06 13:37 ` Toke Høiland-Jørgensen
2022-10-05 21:48 ` [f2fs-dev] [PATCH v1 3/5] treewide: use get_random_u32() " Jason A. Donenfeld via Linux-f2fs-devel
2022-10-05 21:48 ` Jason A. Donenfeld via Linux-f2fs-devel
2022-10-05 21:48 ` Jason A. Donenfeld
2022-10-05 21:48 ` Jason A. Donenfeld
2022-10-05 21:48 ` Jason A. Donenfeld
2022-10-05 21:48 ` Jason A. Donenfeld
2022-10-05 21:48 ` Jason A. Donenfeld
2022-10-06 8:43 ` [f2fs-dev] " Jan Kara
2022-10-06 8:43 ` Jan Kara
2022-10-06 8:43 ` Jan Kara
2022-10-06 8:43 ` Jan Kara
2022-10-06 8:43 ` Jan Kara
2022-10-06 8:43 ` Jan Kara
2022-10-06 12:33 ` [f2fs-dev] " Jason A. Donenfeld via Linux-f2fs-devel
2022-10-06 12:33 ` Jason A. Donenfeld via dev
2022-10-06 12:33 ` Jason A. Donenfeld
2022-10-06 12:33 ` Jason A. Donenfeld
2022-10-06 12:33 ` Jason A. Donenfeld
2022-10-06 12:33 ` Jason A. Donenfeld
2022-10-06 12:56 ` Andy Shevchenko
2022-10-06 13:01 ` Andy Shevchenko
2022-10-06 13:01 ` Andy Shevchenko
2022-10-06 13:01 ` Andy Shevchenko
2022-10-06 13:01 ` Andy Shevchenko
2022-10-06 13:01 ` Andy Shevchenko
2022-10-06 13:01 ` Andy Shevchenko
2022-10-06 13:07 ` Jason A. Donenfeld
2022-10-06 13:07 ` Jason A. Donenfeld via Linux-f2fs-devel
2022-10-06 13:07 ` [f2fs-dev] " Jason A. Donenfeld
2022-10-06 13:07 ` Jason A. Donenfeld
2022-10-06 13:07 ` Jason A. Donenfeld
2022-10-06 13:07 ` Jason A. Donenfeld
2022-10-06 13:07 ` Jason A. Donenfeld via Linux-f2fs-devel
2022-10-06 12:47 ` Jason Gunthorpe
2022-10-06 12:47 ` Jason Gunthorpe
2022-10-06 12:47 ` Jason Gunthorpe
2022-10-06 12:47 ` Jason Gunthorpe
2022-10-06 12:47 ` Jason Gunthorpe
2022-10-06 12:47 ` [f2fs-dev] " Jason Gunthorpe
2022-10-06 13:05 ` Jason A. Donenfeld via Linux-f2fs-devel
2022-10-06 13:05 ` Jason A. Donenfeld via dev
2022-10-06 13:05 ` Jason A. Donenfeld
2022-10-06 13:05 ` Jason A. Donenfeld
2022-10-06 13:05 ` Jason A. Donenfeld
2022-10-06 13:05 ` Jason A. Donenfeld
2022-10-06 13:15 ` Jason Gunthorpe [this message]
2022-10-06 13:15 ` Jason Gunthorpe
2022-10-06 13:15 ` Jason Gunthorpe
2022-10-06 13:15 ` Jason Gunthorpe
2022-10-06 13:15 ` Jason Gunthorpe
2022-10-06 13:15 ` Jason Gunthorpe
2022-10-06 13:15 ` [f2fs-dev] " Jason Gunthorpe
2022-10-06 13:20 ` Andy Shevchenko
2022-10-06 13:20 ` Andy Shevchenko
2022-10-06 13:20 ` Andy Shevchenko
2022-10-06 13:20 ` Andy Shevchenko
2022-10-06 13:20 ` Andy Shevchenko
2022-10-06 13:20 ` Andy Shevchenko
2022-10-06 13:20 ` Andy Shevchenko
2022-10-06 13:20 ` [f2fs-dev] " Andy Shevchenko
2022-10-06 13:38 ` Toke Høiland-Jørgensen
[not found] ` <20221005214844.2699-4-Jason-OnJsPKxuuEcAvxtiuMwx3w@public.gmane.org>
2022-10-12 19:16 ` Joe Perches
2022-10-12 19:16 ` Joe Perches
2022-10-12 19:16 ` Joe Perches
2022-10-12 19:16 ` Joe Perches
2022-10-12 19:16 ` Joe Perches
2022-10-12 19:16 ` [f2fs-dev] " Joe Perches
2022-10-12 19:16 ` Joe Perches
2022-10-12 19:16 ` Joe Perches
2022-10-12 19:16 ` Joe Perches
2022-10-12 21:29 ` David Laight
2022-10-12 21:29 ` David Laight
2022-10-12 21:29 ` David Laight
2022-10-12 21:29 ` David Laight
2022-10-12 21:29 ` [f2fs-dev] " David Laight
2022-10-12 21:29 ` David Laight
2022-10-12 21:29 ` David Laight
2022-10-12 21:29 ` David Laight
2022-10-13 1:37 ` Joe Perches
2022-10-13 1:37 ` Joe Perches
2022-10-13 1:37 ` Joe Perches
2022-10-13 1:37 ` Joe Perches
2022-10-13 1:37 ` Joe Perches
2022-10-13 1:37 ` Joe Perches
2022-10-13 1:37 ` Joe Perches
2022-10-13 1:37 ` [f2fs-dev] " Joe Perches
2022-10-05 21:48 ` [f2fs-dev] [PATCH v1 4/5] treewide: use get_random_bytes " Jason A. Donenfeld via Linux-f2fs-devel
2022-10-05 21:48 ` Jason A. Donenfeld via Linux-f2fs-devel
2022-10-05 21:48 ` Jason A. Donenfeld
2022-10-05 21:48 ` Jason A. Donenfeld
2022-10-05 21:48 ` Jason A. Donenfeld
2022-10-05 21:48 ` Jason A. Donenfeld
2022-10-05 21:48 ` Jason A. Donenfeld
2022-10-06 4:45 ` [f2fs-dev] " Kees Cook
2022-10-06 4:45 ` Kees Cook
2022-10-06 4:45 ` Kees Cook
2022-10-06 4:45 ` Kees Cook
2022-10-06 4:45 ` Kees Cook
2022-10-06 4:45 ` Kees Cook
2022-10-06 4:48 ` Kees Cook
2022-10-06 4:48 ` Kees Cook
2022-10-06 4:48 ` Kees Cook
2022-10-06 4:48 ` Kees Cook
2022-10-06 4:48 ` Kees Cook
2022-10-06 4:48 ` [f2fs-dev] " Kees Cook
2022-10-05 21:48 ` [f2fs-dev] [PATCH v1 5/5] prandom: remove unused functions Jason A. Donenfeld via Linux-f2fs-devel
2022-10-05 21:48 ` Jason A. Donenfeld via dev
2022-10-05 21:48 ` Jason A. Donenfeld
2022-10-05 21:48 ` Jason A. Donenfeld
2022-10-05 21:48 ` Jason A. Donenfeld
2022-10-05 21:48 ` Jason A. Donenfeld
2022-10-05 21:48 ` Jason A. Donenfeld
2022-10-06 4:39 ` [f2fs-dev] " Kees Cook
2022-10-06 4:39 ` Kees Cook
2022-10-06 4:39 ` Kees Cook
2022-10-06 4:39 ` Kees Cook
2022-10-06 4:39 ` Kees Cook
2022-10-06 4:39 ` Kees Cook
2022-10-06 4:55 ` [PATCH v1 0/5] treewide cleanup of random integer usage Kees Cook
2022-10-06 4:55 ` Kees Cook
2022-10-06 4:55 ` Kees Cook
2022-10-06 4:55 ` Kees Cook
2022-10-06 4:55 ` Kees Cook
2022-10-06 4:55 ` [f2fs-dev] " Kees Cook
2022-10-06 5:40 ` Kees Cook
2022-10-06 5:40 ` Kees Cook
2022-10-06 5:40 ` Kees Cook
2022-10-06 5:40 ` Kees Cook
2022-10-06 5:40 ` Kees Cook
2022-10-06 5:40 ` Kees Cook
2022-10-06 12:53 ` [f2fs-dev] " Jason A. Donenfeld via Linux-f2fs-devel
2022-10-06 12:53 ` Jason A. Donenfeld via dev
2022-10-06 12:53 ` Jason A. Donenfeld
2022-10-06 12:53 ` Jason A. Donenfeld
2022-10-06 12:53 ` Jason A. Donenfeld
2022-10-06 12:53 ` Jason A. Donenfeld
2022-10-06 6:15 ` Kees Cook
2022-10-06 12:58 ` Jason A. Donenfeld
2022-10-06 8:17 ` Yann Droneaud
2022-10-06 13:49 ` [f2fs-dev] " Jason A. Donenfeld via Linux-f2fs-devel
2022-10-06 13:49 ` Jason A. Donenfeld
2022-10-06 13:49 ` Jason A. Donenfeld
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Yz7U99PPl8uHCLFY@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=Jason@zx2c4.com \
--cc=SHA-cyfmac-dev-list@infineon.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=cake@lists.bufferbloat.net \
--cc=ceph-devel@vger.kernel.org \
--cc=coreteam@netfilter.org \
--cc=dccp@vger.kernel.org \
--cc=dev@openvswitch.org \
--cc=dmaengine@vger.kernel.org \
--cc=drbd-dev@lists.linbit.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kasan-dev@googlegroups.com \
--cc=linux-actions@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-hams@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-raid@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-sctp@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux-usb@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lvs-devel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=rds-devel@oss.oracle.com \
--cc=target-devel@vger.kernel.org \
--cc=tipc-discussion@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.