Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1739852 > unrolled thread

Unreviewed arm64 ABI change in linux-next via driver-core tree

Back to article view | Back to linux.kernel

Contents

  Unreviewed arm64 ABI change in linux-next via driver-core tree Will Deacon <will.deacon@arm.com> - 2017-09-26 14:50 +0200
    Re: Unreviewed arm64 ABI change in linux-next via driver-core tree Felix Schnizlein <fschnizlein@suse.com> - 2017-09-26 15:00 +0200
    Re: Unreviewed arm64 ABI change in linux-next via driver-core tree Mark Rutland <mark.rutland@arm.com> - 2017-09-26 15:20 +0200
      Re: Unreviewed arm64 ABI change in linux-next via driver-core tree Felix Schnizlein <fschnizlein@suse.com> - 2017-09-26 15:30 +0200
      Re: Unreviewed arm64 ABI change in linux-next via driver-core tree Greg KH <gregkh@linuxfoundation.org> - 2017-09-26 23:30 +0200

#1739852 — Unreviewed arm64 ABI change in linux-next via driver-core tree

Hi Greg,

We stumbled over a change in linux-next that has ABI implications for arm64
and, as far as we can tell, has not been reviewed:

https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/arch/arm64/kernel?id=fb7ff3f8721b87bf078868c9a252fa0cf71a47c2

("fb7ff3f8721b cpuinfo: implement sysfs nodes for arm64")

It looks like this was requested by you on LKML here:

https://lkml.org/lkml/2017/8/2/663

but these sorts of changes really need to go on the linux-arm-kernel mailing
list with the maintainers on cc so that the patches can be properly reviewed
and eventually acked if appropriate. In this case, I can't find any trace of
the patch on any of the mailing lists to which I'm subscribed.

Please can you drop this from your tree until we've had a chance to review
it properly? If Felix can repost it as above, then we can get the discussion
started because, aside from this email, we have concerns about exactly what
is being exposed to userspace here.

Thanks,

Will

[toc] | [next] | [standalone]

#1739867

[Multipart message — attachments visible in raw view] — view raw

Hi Will, Hi Greg,

It seems this is all my fault. It looks like forgot to check that the
outgoing mailserver send the patches correctly to the mailinglists which
doesn't happen.

So to make this horrible situation short maybe drop the patches and I
will resend them and make sure this time everything works as expected

Sorry Greg for all the stress :(

Felix
On 26.09.17, Will Deacon wrote:
> Hi Greg,
> 
> We stumbled over a change in linux-next that has ABI implications for arm64
> and, as far as we can tell, has not been reviewed:
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/arch/arm64/kernel?id=fb7ff3f8721b87bf078868c9a252fa0cf71a47c2
> 
> ("fb7ff3f8721b cpuinfo: implement sysfs nodes for arm64")
> 
> It looks like this was requested by you on LKML here:
> 
> https://lkml.org/lkml/2017/8/2/663
> 
> but these sorts of changes really need to go on the linux-arm-kernel mailing
> list with the maintainers on cc so that the patches can be properly reviewed
> and eventually acked if appropriate. In this case, I can't find any trace of
> the patch on any of the mailing lists to which I'm subscribed.
> 
> Please can you drop this from your tree until we've had a chance to review
> it properly? If Felix can repost it as above, then we can get the discussion
> started because, aside from this email, we have concerns about exactly what
> is being exposed to userspace here.
> 
> Thanks,
> 
> Will
> 

[toc] | [prev] | [next] | [standalone]

#1739882

Hi,

On Tue, Sep 26, 2017 at 01:45:37PM +0100, Will Deacon wrote:
> Hi Greg,
> 
> We stumbled over a change in linux-next that has ABI implications for arm64
> and, as far as we can tell, has not been reviewed:
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/arch/arm64/kernel?id=fb7ff3f8721b87bf078868c9a252fa0cf71a47c2
> 
> ("fb7ff3f8721b cpuinfo: implement sysfs nodes for arm64")

> Please can you drop this from your tree until we've had a chance to review
> it properly? If Felix can repost it as above, then we can get the discussion
> started because, aside from this email, we have concerns about exactly what
> is being exposed to userspace here.

Seconded.

Experience with the existing /proc/cpuinfo shows that this needs *very*
careful review.

I've worked on arm64's /proc/cpuinfo, and I'd appreciate being Cc'd on
future postings of this series. I'd also recommend that future postings
are also Cc'd to linux-arch (and maybe linux-api) so that the interface
is reviewed by a larger set of relevant parties.

Thanks,
Mark.

[toc] | [prev] | [next] | [standalone]

#1739885

[Multipart message — attachments visible in raw view] — view raw

On 26.09.17, Mark Rutland wrote:
> Hi,
> 
> On Tue, Sep 26, 2017 at 01:45:37PM +0100, Will Deacon wrote:
> > Hi Greg,
> > 
> > We stumbled over a change in linux-next that has ABI implications for arm64
> > and, as far as we can tell, has not been reviewed:
> > 
> > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/arch/arm64/kernel?id=fb7ff3f8721b87bf078868c9a252fa0cf71a47c2
> > 
> > ("fb7ff3f8721b cpuinfo: implement sysfs nodes for arm64")
> 
> > Please can you drop this from your tree until we've had a chance to review
> > it properly? If Felix can repost it as above, then we can get the discussion
> > started because, aside from this email, we have concerns about exactly what
> > is being exposed to userspace here.
> 
> Seconded.
> 
> Experience with the existing /proc/cpuinfo shows that this needs *very*
> careful review.
> 
> I've worked on arm64's /proc/cpuinfo, and I'd appreciate being Cc'd on
> future postings of this series. I'd also recommend that future postings
> are also Cc'd to linux-arch (and maybe linux-api) so that the interface
> is reviewed by a larger set of relevant parties.

I will do that!
> 
> Thanks,
> Mark.

[toc] | [prev] | [next] | [standalone]

#1740218

On Tue, Sep 26, 2017 at 02:15:26PM +0100, Mark Rutland wrote:
> Hi,
> 
> On Tue, Sep 26, 2017 at 01:45:37PM +0100, Will Deacon wrote:
> > Hi Greg,
> > 
> > We stumbled over a change in linux-next that has ABI implications for arm64
> > and, as far as we can tell, has not been reviewed:
> > 
> > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/arch/arm64/kernel?id=fb7ff3f8721b87bf078868c9a252fa0cf71a47c2
> > 
> > ("fb7ff3f8721b cpuinfo: implement sysfs nodes for arm64")
> 
> > Please can you drop this from your tree until we've had a chance to review
> > it properly? If Felix can repost it as above, then we can get the discussion
> > started because, aside from this email, we have concerns about exactly what
> > is being exposed to userspace here.
> 
> Seconded.

Now dropped.

> Experience with the existing /proc/cpuinfo shows that this needs *very*
> careful review.

Hah, yes, but with a sysfs interface, one would "hope" that you can get
it right this time around :)

> I've worked on arm64's /proc/cpuinfo, and I'd appreciate being Cc'd on
> future postings of this series. I'd also recommend that future postings
> are also Cc'd to linux-arch (and maybe linux-api) so that the interface
> is reviewed by a larger set of relevant parties.

For some reason, this set of patches never made it to lkml or the lists
multiple times.  Both you all, and the x86 developers have objected to
these changes, so they are gone for now.

Felix, please resend the series and cc: the needed people.

thanks,

greg k-h

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web