On Tue, 8 May 2018, Sasha Levin wrote:
There's no one, for example, who picked up vanilla v4.16 and plans to
keep using it for a year.
Actually, at a prior job I would do almost exactly that.
I never intended to go a year without updating, but it would happen if nothing
came up that was
On Tue, 8 May 2018, Sasha Levin wrote:
There's no one, for example, who picked up vanilla v4.16 and plans to
keep using it for a year.
Actually, at a prior job I would do almost exactly that.
I never intended to go a year without updating, but it would happen if nothing
came up that was
the 4.4.112 patches that Greg just posted include a bunch of work for these
vulnerabilities.
Who knows what has been backported to the kernel he is running.
k
the 4.4.112 patches that Greg just posted include a bunch of work for these
vulnerabilities.
Who knows what has been backported to the kernel he is running.
k
you are running a RedHat kernel, you will have to ask them about what they have
included in it.
k
you are running a RedHat kernel, you will have to ask them about what they have
included in it.
k
I somewhat hate to ask this, but for those of us following at home, what does
this add to the overhead?
I am remembering an estimate from mid last week that put retpoline at replacing
a 3 clock 'ret' with 30 clocks of eye-bleed code
I somewhat hate to ask this, but for those of us following at home, what does
this add to the overhead?
I am remembering an estimate from mid last week that put retpoline at replacing
a 3 clock 'ret' with 30 clocks of eye-bleed code
The point is that in many cases, if someone explits the "trusted" process, they
already have everything that the machine is able to do anyway.
The point is that in many cases, if someone explits the "trusted" process, they
already have everything that the machine is able to do anyway.
.
David Lang
.
David Lang
edent" and if the
violating of the Linux license agreement is left unchecked, then quite
possibly a precedent could be set to allow an entire upstream kernel
to be co-opted.
This is a potential problem.
David Lang
edent" and if the
violating of the Linux license agreement is left unchecked, then quite
possibly a precedent could be set to allow an entire upstream kernel
to be co-opted.
This is a potential problem.
David Lang
copyleft-next and just use GPLv2
David Lang
copyleft-next and just use GPLv2
David Lang
what's local and what's remote, that list would become out of date as new
filesystems are added)
David Lang
, that list would become out of date as new
filesystems are added)
David Lang
types find comforting.
What does SRE stand for?
Site Reliability Engineer, a mix of operations and engineering (DevOps++)
David Lang
types find comforting.
What does SRE stand for?
Site Reliability Engineer, a mix of operations and engineering (DevOps++)
David Lang
s here not to depend on this"
Drive ordering has been stable since the 0.1 kernel [1]
It takes a lot longer to detect USB drives, why in the world would they be
detected before hard-wired drives?
I expect that Linus' response is going to be very quotable.
David Lang
[1] given s
ordering has been stable since the 0.1 kernel [1]
It takes a lot longer to detect USB drives, why in the world would they be
detected before hard-wired drives?
I expect that Linus' response is going to be very quotable.
David Lang
[1] given stable hardware and no new drivers becoming involved
rogram that will run a program inside an existing
namespace. It looks like you need something similar that implements some
permission checking (only let you go into namespaces of other programs for the
same user or similar), but you should be able to make proof-of-concept scripts
with nsenter.
David Lang
an existing
namespace. It looks like you need something similar that implements some
permission checking (only let you go into namespaces of other programs for the
same user or similar), but you should be able to make proof-of-concept scripts
with nsenter.
David Lang
daemon to run as root that
reassigns your different sessions from one ns to another.
David Lang
When we originally looked at namespaces and containers, we could not
find a solution to achieve the above. Is this possible using
namespaces?
Regards
/Cole
that
reassigns your different sessions from one ns to another.
David Lang
When we originally looked at namespaces and containers, we could not
find a solution to achieve the above. Is this possible using
namespaces?
Regards
/Cole
talled that would be separate from the system packages, and no
collisions would
occur.
why would this not be a case to use filesystem namespaces and bind mounts?
David Lang
from the system packages, and no
collisions would
occur.
why would this not be a case to use filesystem namespaces and bind mounts?
David Lang
what is ACPICA and why should we care about divergence between it and the linux
upstream? Where is it to be found?
This may be common knowlege to many people, but it should probably be documented
in the patch bundle and it's explination.
David Lang
On Tue, 29 Dec 2015, Lv Zheng wrote
what is ACPICA and why should we care about divergence between it and the linux
upstream? Where is it to be found?
This may be common knowlege to many people, but it should probably be documented
in the patch bundle and it's explination.
David Lang
On Tue, 29 Dec 2015, Lv Zheng wrote
and kill the system without
providing a kernel level mechanism to limit the damage (as opposed to fixing
individual apps) seems rather short-sighted at best.
David Lang
providing a kernel level mechanism to limit the damage (as opposed to fixing
individual apps) seems rather short-sighted at best.
David Lang
On Fri, 31 Jul 2015, Daniel Phillips wrote:
On Friday, July 31, 2015 11:29:51 AM PDT, David Lang wrote:
We, the Linux Community have less tolerance for losing people's data and
preventing them from operating than we used to when it was all tinkerer's
personal data and secondary systems.
So
evelopment as still being high, just with more testing and
polishing before it gets out to users.
David Lang
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org
as still being high, just with more testing and
polishing before it gets out to users.
David Lang
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please
On Fri, 31 Jul 2015, Daniel Phillips wrote:
On Friday, July 31, 2015 11:29:51 AM PDT, David Lang wrote:
We, the Linux Community have less tolerance for losing people's data and
preventing them from operating than we used to when it was all tinkerer's
personal data and secondary systems.
So
On Wed, 24 Jun 2015, Greg KH wrote:
On Wed, Jun 24, 2015 at 10:39:52AM -0700, David Lang wrote:
On Wed, 24 Jun 2015, Ingo Molnar wrote:
And the thing is, in hindsight, after such huge flamewars, years down the line,
almost never do I see the following question asked: 'what were we thinking
On Wed, 24 Jun 2015, Greg KH wrote:
On Wed, Jun 24, 2015 at 10:39:52AM -0700, David Lang wrote:
On Wed, 24 Jun 2015, Ingo Molnar wrote:
And the thing is, in hindsight, after such huge flamewars, years down the line,
almost never do I see the following question asked: 'what were we thinking
On Wed, 24 Jun 2015, Martin Steigerwald wrote:
Am Mittwoch, 24. Juni 2015, 10:39:52 schrieb David Lang:
On Wed, 24 Jun 2015, Ingo Molnar wrote:
And the thing is, in hindsight, after such huge flamewars, years down
the line, almost never do I see the following question asked: 'what
were we
fuss about?'. So I think by and large the process works.
counterexamples, devfs, tux
David Lang
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.h
fuss about?'. So I think by and large the process works.
counterexamples, devfs, tux
David Lang
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please
On Wed, 24 Jun 2015, Martin Steigerwald wrote:
Am Mittwoch, 24. Juni 2015, 10:39:52 schrieb David Lang:
On Wed, 24 Jun 2015, Ingo Molnar wrote:
And the thing is, in hindsight, after such huge flamewars, years down
the line, almost never do I see the following question asked: 'what
were we
for what
you'd like to do with it, i.e. I don't know what the problem is.
As I understand things, the problem is ~providing RAID across multiple machines,
not just across the disks in one machine.
David Lang
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" i
for what
you'd like to do with it, i.e. I don't know what the problem is.
As I understand things, the problem is ~providing RAID across multiple machines,
not just across the disks in one machine.
David Lang
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body
that.
Arguing license issues and at the same time claiming that you should ignore a
legal statement like the footer is a bit odd.
David Lang
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majo
is whole discussion assumes that the DTB is even copyrightable. Since
it's intended to be strictly a functional description of what the hardware is
able to do, that could be questioned
David Lang
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a m
that.
Arguing license issues and at the same time claiming that you should ignore a
legal statement like the footer is a bit odd.
David Lang
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
copyrightable. Since
it's intended to be strictly a functional description of what the hardware is
able to do, that could be questioned
David Lang
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info
On Mon, 25 May 2015, Daniel Phillips wrote:
On Monday, May 25, 2015 11:04:39 PM PDT, David Lang wrote:
if the page gets modified again, will that cause any issues? what if the
page gets modified before the copy gets written out, so that there are two
dirty copies of the page in the process
On Mon, 25 May 2015, Daniel Phillips wrote:
On Monday, May 25, 2015 9:25:44 PM PDT, Rik van Riel wrote:
On 05/21/2015 03:53 PM, Daniel Phillips wrote:
On Wednesday, May 20, 2015 8:51:46 PM PDT, David Lang wrote:
how do you prevent it from continuing to interact with the old version
On Mon, 25 May 2015, Daniel Phillips wrote:
On Monday, May 25, 2015 9:25:44 PM PDT, Rik van Riel wrote:
On 05/21/2015 03:53 PM, Daniel Phillips wrote:
On Wednesday, May 20, 2015 8:51:46 PM PDT, David Lang wrote:
how do you prevent it from continuing to interact with the old version
On Mon, 25 May 2015, Daniel Phillips wrote:
On Monday, May 25, 2015 11:04:39 PM PDT, David Lang wrote:
if the page gets modified again, will that cause any issues? what if the
page gets modified before the copy gets written out, so that there are two
dirty copies of the page in the process
should be surprised. That is a race even without page fork.
how do you prevent it from continuing to interact with the old version of the
page and never see updates or have it's changes reflected on the current page?
David Lang
--
To unsubscribe from this list: send the line "unsubscribe
with other things
touching the page cache.
David Lang
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
with other things
touching the page cache.
David Lang
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
should be surprised. That is a race even without page fork.
how do you prevent it from continuing to interact with the old version of the
page and never see updates or have it's changes reflected on the current page?
David Lang
--
To unsubscribe from this list: send the line unsubscribe linux
if your implementation details make it safe, these need to be safe even
without your implementation details to be acceptable in the core kernel.
David Lang
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More
if your implementation details make it safe, these need to be safe even
without your implementation details to be acceptable in the core kernel.
David Lang
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo
follow-up writes if it's modified again
otherwise, won't this be the same thing?
David Lang
If RDMA to a mmapped file races with write(2) to the same file,
maybe it is reasonable and expected to lose some data.
In the RDMA case, there is at least application awareness to work around
th
writes if it's modified again
otherwise, won't this be the same thing?
David Lang
If RDMA to a mmapped file races with write(2) to the same file,
maybe it is reasonable and expected to lose some data.
In the RDMA case, there is at least application awareness to work around
the problems
On Tue, 12 May 2015, Daniel Phillips wrote:
On 05/12/2015 02:30 PM, David Lang wrote:
On Tue, 12 May 2015, Daniel Phillips wrote:
Phoronix published a headline that identifies Dave Chinner as
someone who takes shots at other projects. Seems pretty much on
the money to me, and it ought
On Tue, 12 May 2015, Daniel Phillips wrote:
On 05/12/2015 11:39 AM, David Lang wrote:
On Mon, 11 May 2015, Daniel Phillips wrote:
...it's the mm and core kernel developers that need to
review and accept that code *before* we can consider merging tux3.
Please do not say "we" whe
you are wrong in your belief, just that you may not be right,
and nobody will know until you are to a usable state and other people can start
beating on it.
David Lang
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@v
are to a usable state and other people can start
beating on it.
David Lang
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http
On Tue, 12 May 2015, Daniel Phillips wrote:
On 05/12/2015 11:39 AM, David Lang wrote:
On Mon, 11 May 2015, Daniel Phillips wrote:
...it's the mm and core kernel developers that need to
review and accept that code *before* we can consider merging tux3.
Please do not say we when you know
On Tue, 12 May 2015, Daniel Phillips wrote:
On 05/12/2015 02:30 PM, David Lang wrote:
On Tue, 12 May 2015, Daniel Phillips wrote:
Phoronix published a headline that identifies Dave Chinner as
someone who takes shots at other projects. Seems pretty much on
the money to me, and it ought
ly modest rate per directory)
And when you then decide that you have to move the directory/file info, doesn't
that create a potentially large amount of unexpected IO that could end up
interfering with what the user is trying to do?
David Lang
--
To unsubscribe from this list: send the lin
then decide that you have to move the directory/file info, doesn't
that create a potentially large amount of unexpected IO that could end up
interfering with what the user is trying to do?
David Lang
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message
On Thu, 7 May 2015, Austin S Hemmelgarn wrote:
On 2015-05-06 16:49, David Lang wrote:
On Wed, 6 May 2015, linuxcbon linuxcbon wrote:
On Wed, May 6, 2015 at 7:53 PM, David Lang wrote:
It's perfectly legitimate to not want to use udev, but that doesn't mean
that the kernel will (or should
On Thu, 7 May 2015, Austin S Hemmelgarn wrote:
On 2015-05-06 16:49, David Lang wrote:
On Wed, 6 May 2015, linuxcbon linuxcbon wrote:
On Wed, May 6, 2015 at 7:53 PM, David Lang da...@lang.hm wrote:
It's perfectly legitimate to not want to use udev, but that doesn't mean
that the kernel
On Wed, 6 May 2015, linuxcbon linuxcbon wrote:
On Wed, May 6, 2015 at 7:53 PM, David Lang wrote:
It's perfectly legitimate to not want to use udev, but that doesn't mean
that the kernel will (or should) do it for you.
David Lang
When I boot the kernel without modules, I don't have anything
perfectly legitimate to not want to use udev, but that doesn't mean that
the kernel will (or should) do it for you.
David Lang
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at ht
On Wed, 6 May 2015, linuxcbon linuxcbon wrote:
On Wed, May 6, 2015 at 7:53 PM, David Lang da...@lang.hm wrote:
It's perfectly legitimate to not want to use udev, but that doesn't mean
that the kernel will (or should) do it for you.
David Lang
When I boot the kernel without modules, I don't
.
It's perfectly legitimate to not want to use udev, but that doesn't mean that
the kernel will (or should) do it for you.
David Lang
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
feeds with one always being a subset of the other,
create a mechanism to allow an arbitrary number of feeds that can be filtered in
different ways
David Lang
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.
a mechanism to allow an arbitrary number of feeds that can be filtered in
different ways
David Lang
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
it unless a vendor waves money.
what drives are available now? see if you can get a couple (either directly or
donated)
David Lang
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at ht
a vendor waves money.
what drives are available now? see if you can get a couple (either directly or
donated)
David Lang
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org
On Thu, 30 Apr 2015, Dave Airlie wrote:
On 30 April 2015 at 10:05, David Lang wrote:
On Wed, 29 Apr 2015, Theodore Ts'o wrote:
On Wed, Apr 29, 2015 at 12:26:59PM -0400, John Stoffel wrote:
If your customers wnat this feature, you're more than welcome to fork
the kernel and support
speed up boot" push started.
Admittedly, this wasn't a stock distro boot/install, it was my own optimized
one, but it also wasn't as optimized and automated as it could have been
(several points where the installer needed to pick items from a menu and enter
values)
David Lang
--
To u
On Wed, 29 Apr 2015, Andy Lutomirski wrote:
On Wed, Apr 29, 2015 at 1:15 PM, David Lang wrote:
On Wed, 29 Apr 2015, Andy Lutomirski wrote:
On Wed, Apr 29, 2015 at 12:30 PM, Austin S Hemmelgarn
wrote:
On 2015-04-29 14:54, Andy Lutomirski wrote:
On Apr 29, 2015 5:48 AM, "Harald
a valid choice. But preventing a receiver from exiting because
it hasn't processed a message is not a valid choice.
David Lang
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vg
.
I've been getting the early boot messages in my logs for decades (assuming the
system doesn't fail before the syslog daemon is started). It sometimes has
required setting a larger than default ringbuffer in the kernel, but that's easy
enough to do.
David Lang
--
To unsubscribe from this list
.
I've been getting the early boot messages in my logs for decades (assuming the
system doesn't fail before the syslog daemon is started). It sometimes has
required setting a larger than default ringbuffer in the kernel, but that's easy
enough to do.
David Lang
--
To unsubscribe from this list
a valid choice. But preventing a receiver from exiting because
it hasn't processed a message is not a valid choice.
David Lang
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
On Wed, 29 Apr 2015, Andy Lutomirski wrote:
On Wed, Apr 29, 2015 at 1:15 PM, David Lang da...@lang.hm wrote:
On Wed, 29 Apr 2015, Andy Lutomirski wrote:
On Wed, Apr 29, 2015 at 12:30 PM, Austin S Hemmelgarn
ahferro...@gmail.com wrote:
On 2015-04-29 14:54, Andy Lutomirski wrote:
On Apr
up boot push started.
Admittedly, this wasn't a stock distro boot/install, it was my own optimized
one, but it also wasn't as optimized and automated as it could have been
(several points where the installer needed to pick items from a menu and enter
values)
David Lang
--
To unsubscribe from
On Thu, 30 Apr 2015, Dave Airlie wrote:
On 30 April 2015 at 10:05, David Lang da...@lang.hm wrote:
On Wed, 29 Apr 2015, Theodore Ts'o wrote:
On Wed, Apr 29, 2015 at 12:26:59PM -0400, John Stoffel wrote:
If your customers wnat this feature, you're more than welcome to fork
the kernel
On Tue, 28 Apr 2015, Havoc Pennington wrote:
On Tue, Apr 28, 2015 at 1:19 PM, David Lang wrote:
If the examples that are being used to show the performance advantage of
kdbus vs normal dbus are doing the wrong thing, then we need to get some
other examples available to people who don't live
l developers can see what you think is the real problem
and how kdbus addresses it.
So far, this 'wrong' example is the only thing that's been posted to show the
performance advantage of kdbus.
David Lang
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
t
On Tue, 28 Apr 2015, Havoc Pennington wrote:
On Tue, Apr 28, 2015 at 1:19 PM, David Lang da...@lang.hm wrote:
If the examples that are being used to show the performance advantage of
kdbus vs normal dbus are doing the wrong thing, then we need to get some
other examples available to people who
you think is the real problem
and how kdbus addresses it.
So far, this 'wrong' example is the only thing that's been posted to show the
performance advantage of kdbus.
David Lang
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord
the maximum number of pending replies per connection.
aren't we being told that part of the reason for needing kdbus is that
thousands, or tens of thousands of messages are being spewed out? how does
limiting it to 128 messages represent real-life if this is the case?
David Lang
The test
), otherwise we can
exceed the maximum number of pending replies per connection.
aren't we being told that part of the reason for needing kdbus is that
thousands, or tens of thousands of messages are being spewed out? how does
limiting it to 128 messages represent real-life if this is the case?
David
e upgraded to fix bugs
that are discovered is a problem.
This is an issue that the Internet of Things folks are just starting to notice,
and it's only going to get worse before it gets better.
How do you patch bugs on your non-volitile media? What keeps that mechansim from
being abused.
abused.
David Lang
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
etimes you have types of controls that are
orthoginal to each other, and you either manage the two types of things in
separate hierarchies, or you end up with one hierarchy that is a permutation of
all the combinations of what would have been separate hierarchies.
David Lang
--
To unsubs
have types of controls that are
orthoginal to each other, and you either manage the two types of things in
separate hierarchies, or you end up with one hierarchy that is a permutation of
all the combinations of what would have been separate hierarchies.
David Lang
--
To unsubscribe from this list
r all resource types.
David Lang
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
specification for the
real-world way in which permissions are managed, and it's called the
FLASK model.
On this topic it's also worth reading Neil Brown's series of articles on this
over at http://lwn.net/Articles/604609/ and why he concludes that having a
single hierarchy for all resource types.
David
1 - 100 of 620 matches
Mail list logo
