Message ID | 097bc300a5c6554ca6fd1886421bb2e0adb03420.1559580831.git.andreyknvl@google.com (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
Series | arm64: untag user pointers passed to the kernel | expand |
On 6/3/19 10:55 AM, Andrey Konovalov wrote: > To allow arm64 syscalls to accept tagged pointers from userspace, we must > untag them when they are passed to the kernel. Since untagging is done in > generic parts of the kernel, the untagged_addr macro needs to be defined > for all architectures. > > Define it as a noop for architectures other than arm64. > > Acked-by: Catalin Marinas <catalin.marinas@arm.com> > Reviewed-by: Khalid Aziz <khalid.aziz@oracle.com> > Signed-off-by: Andrey Konovalov <andreyknvl@google.com> > --- > include/linux/mm.h | 4 ++++ > 1 file changed, 4 insertions(+) > > diff --git a/include/linux/mm.h b/include/linux/mm.h > index 0e8834ac32b7..949d43e9c0b6 100644 > --- a/include/linux/mm.h > +++ b/include/linux/mm.h > @@ -99,6 +99,10 @@ extern int mmap_rnd_compat_bits __read_mostly; > #include <asm/pgtable.h> > #include <asm/processor.h> > > +#ifndef untagged_addr > +#define untagged_addr(addr) (addr) > +#endif > + > #ifndef __pa_symbol > #define __pa_symbol(x) __pa(RELOC_HIDE((unsigned long)(x), 0)) > #endif > Andrey, This patch has now become part of the other patch series Chris Hellwig has sent out - <https://lore.kernel.org/lkml/20190601074959.14036-1-hch@lst.de/>. Can you coordinate with that patch series? -- Khalid
On Mon, Jun 3, 2019 at 7:04 PM Khalid Aziz <khalid.aziz@oracle.com> wrote: > > On 6/3/19 10:55 AM, Andrey Konovalov wrote: > > To allow arm64 syscalls to accept tagged pointers from userspace, we must > > untag them when they are passed to the kernel. Since untagging is done in > > generic parts of the kernel, the untagged_addr macro needs to be defined > > for all architectures. > > > > Define it as a noop for architectures other than arm64. > > > > Acked-by: Catalin Marinas <catalin.marinas@arm.com> > > Reviewed-by: Khalid Aziz <khalid.aziz@oracle.com> > > Signed-off-by: Andrey Konovalov <andreyknvl@google.com> > > --- > > include/linux/mm.h | 4 ++++ > > 1 file changed, 4 insertions(+) > > > > diff --git a/include/linux/mm.h b/include/linux/mm.h > > index 0e8834ac32b7..949d43e9c0b6 100644 > > --- a/include/linux/mm.h > > +++ b/include/linux/mm.h > > @@ -99,6 +99,10 @@ extern int mmap_rnd_compat_bits __read_mostly; > > #include <asm/pgtable.h> > > #include <asm/processor.h> > > > > +#ifndef untagged_addr > > +#define untagged_addr(addr) (addr) > > +#endif > > + > > #ifndef __pa_symbol > > #define __pa_symbol(x) __pa(RELOC_HIDE((unsigned long)(x), 0)) > > #endif > > > > Andrey, > > This patch has now become part of the other patch series Chris Hellwig > has sent out - > <https://lore.kernel.org/lkml/20190601074959.14036-1-hch@lst.de/>. Can > you coordinate with that patch series? Hi! Yes, I've seen it. How should I coordinate? Rebase this series on top of that one? Thanks! > > -- > Khalid >
On 6/3/19 11:06 AM, Andrey Konovalov wrote: > On Mon, Jun 3, 2019 at 7:04 PM Khalid Aziz <khalid.aziz@oracle.com> wrote: >> Andrey, >> >> This patch has now become part of the other patch series Chris Hellwig >> has sent out - >> <https://lore.kernel.org/lkml/20190601074959.14036-1-hch@lst.de/>. Can >> you coordinate with that patch series? > > Hi! > > Yes, I've seen it. How should I coordinate? Rebase this series on top > of that one? That would be one way to do it. Better yet, separate this patch from both patch series, make it standalone and then rebase the two patch series on top of it. -- Khalid
On Mon, Jun 03, 2019 at 11:24:35AM -0600, Khalid Aziz wrote: > On 6/3/19 11:06 AM, Andrey Konovalov wrote: > > On Mon, Jun 3, 2019 at 7:04 PM Khalid Aziz <khalid.aziz@oracle.com> wrote: > >> Andrey, > >> > >> This patch has now become part of the other patch series Chris Hellwig > >> has sent out - > >> <https://lore.kernel.org/lkml/20190601074959.14036-1-hch@lst.de/>. Can > >> you coordinate with that patch series? > > > > Hi! > > > > Yes, I've seen it. How should I coordinate? Rebase this series on top > > of that one? > > That would be one way to do it. Better yet, separate this patch from > both patch series, make it standalone and then rebase the two patch > series on top of it. I think easiest would be to just ask Linus if he could make an exception and include this trivial prep patch in 5.2-rc.
On 6/3/19 11:29 AM, Christoph Hellwig wrote: > On Mon, Jun 03, 2019 at 11:24:35AM -0600, Khalid Aziz wrote: >> On 6/3/19 11:06 AM, Andrey Konovalov wrote: >>> On Mon, Jun 3, 2019 at 7:04 PM Khalid Aziz <khalid.aziz@oracle.com> wrote: >>>> Andrey, >>>> >>>> This patch has now become part of the other patch series Chris Hellwig >>>> has sent out - >>>> <https://lore.kernel.org/lkml/20190601074959.14036-1-hch@lst.de/>. Can >>>> you coordinate with that patch series? >>> >>> Hi! >>> >>> Yes, I've seen it. How should I coordinate? Rebase this series on top >>> of that one? >> >> That would be one way to do it. Better yet, separate this patch from >> both patch series, make it standalone and then rebase the two patch >> series on top of it. > > I think easiest would be to just ask Linus if he could make an exception > and include this trivial prep patch in 5.2-rc. > Andrey, Would you mind updating the commit log to make it not arm64 specific and sending this patch out by itself. We can then ask Linus if he can include just this patch in the next rc. Thanks, Khalid
On Mon, Jun 3, 2019 at 8:17 PM Khalid Aziz <khalid.aziz@oracle.com> wrote: > > On 6/3/19 11:29 AM, Christoph Hellwig wrote: > > On Mon, Jun 03, 2019 at 11:24:35AM -0600, Khalid Aziz wrote: > >> On 6/3/19 11:06 AM, Andrey Konovalov wrote: > >>> On Mon, Jun 3, 2019 at 7:04 PM Khalid Aziz <khalid.aziz@oracle.com> wrote: > >>>> Andrey, > >>>> > >>>> This patch has now become part of the other patch series Chris Hellwig > >>>> has sent out - > >>>> <https://lore.kernel.org/lkml/20190601074959.14036-1-hch@lst.de/>. Can > >>>> you coordinate with that patch series? > >>> > >>> Hi! > >>> > >>> Yes, I've seen it. How should I coordinate? Rebase this series on top > >>> of that one? > >> > >> That would be one way to do it. Better yet, separate this patch from > >> both patch series, make it standalone and then rebase the two patch > >> series on top of it. > > > > I think easiest would be to just ask Linus if he could make an exception > > and include this trivial prep patch in 5.2-rc. > > > > Andrey, > > Would you mind updating the commit log to make it not arm64 specific and > sending this patch out by itself. We can then ask Linus if he can > include just this patch in the next rc. Sure! Just sent it out. > > Thanks, > Khalid >
diff --git a/include/linux/mm.h b/include/linux/mm.h index 0e8834ac32b7..949d43e9c0b6 100644 --- a/include/linux/mm.h +++ b/include/linux/mm.h @@ -99,6 +99,10 @@ extern int mmap_rnd_compat_bits __read_mostly; #include <asm/pgtable.h> #include <asm/processor.h> +#ifndef untagged_addr +#define untagged_addr(addr) (addr) +#endif + #ifndef __pa_symbol #define __pa_symbol(x) __pa(RELOC_HIDE((unsigned long)(x), 0)) #endif