Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #59989 > unrolled thread
| Started by | Ben Hutchings <ben@decadent.org.uk> |
|---|---|
| First post | 2018-01-15 00:10 +0100 |
| Last post | 2018-01-16 19:00 +0100 |
| Articles | 3 — 2 participants |
Back to article view | Back to linux.debian.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Bug#886630: linux-image-3.2.0-5-amd64 Kernel panic after upgrading when use hidepid Debian wheezy Ben Hutchings <ben@decadent.org.uk> - 2018-01-15 00:10 +0100
Bug#887106: Bug#886630: linux-image-3.2.0-5-amd64 Kernel panic after upgrading when use hidepid Debian wheezy Niels Hendriks <niels@nuvini.com> - 2018-01-16 14:00 +0100
Bug#886630: linux-image-3.2.0-5-amd64 Kernel panic after upgrading when use hidepid Debian wheezy Ben Hutchings <ben@decadent.org.uk> - 2018-01-16 19:00 +0100
| From | Ben Hutchings <ben@decadent.org.uk> |
|---|---|
| Date | 2018-01-15 00:10 +0100 |
| Subject | Bug#886630: linux-image-3.2.0-5-amd64 Kernel panic after upgrading when use hidepid Debian wheezy |
| Message-ID | <v7ZzA-1ne-7@gated-at.bofh.it> |
[Multipart message — attachments visible in raw view] — view raw
Control: tag -1 patch
On Mon, 2018-01-08 at 10:29 +0100, Camilo Echevarne wrote:
[...]
> After updating the linux-image-amd64 system package, when we try to
> mount proc with the hidepid option the server throws a kernel panic.
[...]
This is a warning, not a panic (which would stop the kernel
completely). Still, I assume that the permission denial makes it
impractical to use the system with hidepid enabled.
This problem was not caused by any of the fixes in the latest update,
but by a fix in 3.2.93 that meant I should have updated the backport of
the hidepid feature. However, I added a binary compatibility patch to
avoid problems like this with any out-of-tree users of the API, and
that hid the problem until I bumped the ABI number and removed all the
binary compatibility patches.
I'll fix this in the next upload. As a temporary measure, you can
rebuild the kernel package with the attached patch, by following the
instructions here:
https://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official
Ben.
--
Ben Hutchings
The generation of random numbers is too important to be left to chance.
- Robert Coveyou
[toc] | [next] | [standalone]
| From | Niels Hendriks <niels@nuvini.com> |
|---|---|
| Date | 2018-01-16 14:00 +0100 |
| Subject | Bug#887106: Bug#886630: linux-image-3.2.0-5-amd64 Kernel panic after upgrading when use hidepid Debian wheezy |
| Message-ID | <v8z0l-y7-5@gated-at.bofh.it> |
| In reply to | #59989 |
[Multipart message — attachments visible in raw view] — view raw
Hi Ben, Thanks for your response. Is there any ETA for when the new version will be released ? We'd like to patch the Meltdown vulnerability and also keep hidepid enabled, but currently the system is unusable with this kernel and hidepid enabled. We tried running with wheezy-backports but it seems that kernel doesn't have the meltdown patch yet. We'd prefer not to compile the kernel manually from source. Thank you, Niels Hendriks On 15 January 2018 at 00:02, Ben Hutchings <ben@decadent.org.uk> wrote: > Control: tag -1 patch > > On Mon, 2018-01-08 at 10:29 +0100, Camilo Echevarne wrote: > [...] > > After updating the linux-image-amd64 system package, when we try to > > mount proc with the hidepid option the server throws a kernel panic. > [...] > > This is a warning, not a panic (which would stop the kernel > completely). Still, I assume that the permission denial makes it > impractical to use the system with hidepid enabled. > > This problem was not caused by any of the fixes in the latest update, > but by a fix in 3.2.93 that meant I should have updated the backport of > the hidepid feature. However, I added a binary compatibility patch to > avoid problems like this with any out-of-tree users of the API, and > that hid the problem until I bumped the ABI number and removed all the > binary compatibility patches. > > I'll fix this in the next upload. As a temporary measure, you can > rebuild the kernel package with the attached patch, by following the > instructions here: > https://kernel-handbook.alioth.debian.org/ch-common- > tasks.html#s-common-official > > Ben. > > -- > Ben Hutchings > The generation of random numbers is too important to be left to chance. > - Robert Coveyou >
[toc] | [prev] | [next] | [standalone]
| From | Ben Hutchings <ben@decadent.org.uk> |
|---|---|
| Date | 2018-01-16 19:00 +0100 |
| Message-ID | <v8DGF-3I1-9@gated-at.bofh.it> |
| In reply to | #60007 |
[Multipart message — attachments visible in raw view] — view raw
On Tue, 2018-01-16 at 13:56 +0100, Niels Hendriks wrote: > Hi Ben, > > Thanks for your response. Is there any ETA for when the new version will be > released ? No, there isn't. > We'd like to patch the Meltdown vulnerability and also keep > hidepid enabled, but currently the system is unusable with this kernel and > hidepid enabled. We tried running with wheezy-backports but it seems that > kernel doesn't have the meltdown patch yet. We'd prefer not to compile the > kernel manually from source. [...] wheezy-backports is not supported and will never get any more security updates. Ben. -- Ben Hutchings When in doubt, use brute force. - Ken Thompson
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.kernel
csiph-web