On 11/5/2018 11:53 AM, valdis.kletni...@vt.edu wrote:
On Mon, 05 Nov 2018 11:28:49 -0500, "Austin S. Hemmelgarn" said:
Also, it's probably worth noting that BTRFS doesn't need to decompress
the entire file to read or write blocks in the middle, it splits the
file
On 2018-09-05 04:37, 焦晓冬 wrote:
On Wed, Sep 5, 2018 at 4:04 PM Rogier Wolff wrote:
On Wed, Sep 05, 2018 at 09:39:58AM +0200, Martin Steigerwald wrote:
Rogier Wolff - 05.09.18, 09:08:
So when a mail queuer puts mail the mailq files and the mail processor
can get them out of there intact, nobo
On 2018-06-14 18:50, Daniel Díaz wrote:
As per the documentation, Kernel Samepage Merging (available
since 2.6.32) is a memory-saving de-duplication feature,
enabled by CONFIG_KSM=y and activated via sysfs. More
information can be found here:
https://www.kernel.org/doc/Documentation/vm/ksm.txt
On 2018-02-14 08:21, Benjamin Drung wrote:
Am Mittwoch, den 14.02.2018, 13:09 + schrieb Ard Biesheuvel:
On 14 February 2018 at 12:52, Benjamin Drung
wrote:
Hi,
I am exploring the possibility to store SSH and other keys in UEFI
variables for systems that do not have persistent storage. The
On 2017-12-15 12:24, Vincent Legoll wrote:
Hello,
This looks fine to me. Ard?
Doesn't this break existing configs?
Would adding a "default yes" on the new menuconfig be OK.
If yes, I'd respin it for a v2
Alternatively, would it not make some degree of sense to just turn the
CONFIG_EFI sy
On 2017-08-09 22:39, Nick Terrell wrote:
Add zstd compression and decompression support to BtrFS. zstd at its
fastest level compresses almost as well as zlib, while offering much
faster compression and decompression, approaching lzo speeds.
I benchmarked btrfs with zstd compression against no co
On 2017-08-10 15:25, Hugo Mills wrote:
On Thu, Aug 10, 2017 at 01:41:21PM -0400, Chris Mason wrote:
On 08/10/2017 04:30 AM, Eric Biggers wrote:
Theses benchmarks are misleading because they compress the whole file as a
single stream without resetting the dictionary, which isn't how data will
t
On 2017-08-10 13:24, Eric Biggers wrote:
On Thu, Aug 10, 2017 at 07:32:18AM -0400, Austin S. Hemmelgarn wrote:
On 2017-08-10 04:30, Eric Biggers wrote:
On Wed, Aug 09, 2017 at 07:35:53PM -0700, Nick Terrell wrote:
It can compress at speeds approaching lz4, and quality approaching lzma
On 2017-08-10 07:32, Austin S. Hemmelgarn wrote:
On 2017-08-10 04:30, Eric Biggers wrote:
On Wed, Aug 09, 2017 at 07:35:53PM -0700, Nick Terrell wrote:
It can compress at speeds approaching lz4, and quality approaching lzma.
Well, for a very loose definition of "approaching", and
On 2017-08-10 04:30, Eric Biggers wrote:
On Wed, Aug 09, 2017 at 07:35:53PM -0700, Nick Terrell wrote:
It can compress at speeds approaching lz4, and quality approaching lzma.
Well, for a very loose definition of "approaching", and certainly not at the
same time. I doubt there's a use case f
On 2017-07-26 13:41, Eric Wheeler wrote:
On Wed, 26 Jul 2017, Pavel Machek wrote:
Hi!
Unfortunately, that would mean shifting 400GB data 8KB forward, and
compatibility problems. So I'd prefer adding bcache superblock into
the reserved space, so I can have caching _and_ compatibility with
grub
On 2017-07-22 07:35, Adam Borowski wrote:
On Fri, Jul 21, 2017 at 11:56:21AM -0400, Austin S. Hemmelgarn wrote:
On 2017-07-20 17:27, Nick Terrell wrote:
This patch set adds xxhash, zstd compression, and zstd decompression
modules. It also adds zstd support to BtrFS and SquashFS.
Each patch
ested and had runtime testing running for
about 18 hours now with no issues, so you can add:
Tested-by: Austin S. Hemmelgarn
For patch 1, I've only compile tested it, but had no issues and got no
warnings about it when booting to test 2-4.
For patch 4, I've compile tested it and d
On 2017-07-21 07:16, Austin S. Hemmelgarn wrote:
On 2017-07-20 17:27, Nick Terrell wrote:
Well this is embarrassing, forgot to type anything before hitting send...
Hi all,
This patch set adds xxhash, zstd compression, and zstd decompression
modules. It also adds zstd support to BtrFS and
On 2017-07-20 17:27, Nick Terrell wrote:
Hi all,
This patch set adds xxhash, zstd compression, and zstd decompression
modules. It also adds zstd support to BtrFS and SquashFS.
Each patch has relevant summaries, benchmarks, and tests.
Best,
Nick Terrell
Changelog:
v1 -> v2:
- Make pointer in
On 2017-07-07 23:07, Adam Borowski wrote:
On Sat, Jul 08, 2017 at 01:40:18AM +0200, Adam Borowski wrote:
On Fri, Jul 07, 2017 at 11:17:49PM +, Nick Terrell wrote:
On 7/6/17, 9:32 AM, "Adam Borowski" wrote:
Got a reproducible crash on amd64:
Thanks for the bug report Adam! I'm looking i
On 2017-05-13 19:17, PGNet Dev wrote:
On 5/13/17 3:15 PM, Valentin Vidic wrote:
Try booting without 'hpet=force,verbose clocksource=hpet' and it should
select xen by default:
Nope. Well, not quite ...
With both
'hpet=force,verbose clocksource=hpet'
removed, I end up with
ca
On 2017-04-08 17:07, Adam Borowski wrote:
Unbreaks ARM and possibly other 32-bit architectures.
Fixes: 7d0ef8b4d: Btrfs: update scrub_parity to use u64 stripe_len
Reported-by: Icenowy Zheng
Signed-off-by: Adam Borowski
---
You'd probably want to squash this with Liu's commit, to be nice to fut
On 2017-04-05 16:14, David Howells wrote:
These patches provide a facility by which a variety of avenues by which
userspace can feasibly modify the running kernel image can be locked down.
These include:
(*) No unsigned modules and no modules for which can't validate the
signature.
(*)
On 2017-03-22 21:32, Scot Doyle wrote:
On Wed, 22 Mar 2017, Tim Gardner wrote:
BugLink: http://bugs.launchpad.net/bugs/869017
Console blanking is not enabling DPMS power saving (thereby negating any
power-saving benefit), and is simply turning the screen content blank. This
means that any crash
On 2017-03-22 09:50, Tim Gardner wrote:
BugLink: http://bugs.launchpad.net/bugs/869017
Signed-off-by: Tim Gardner
Cc: Greg Kroah-Hartman
Cc: Jiri Slaby
Cc: Adam Borowski
Cc: Scot Doyle
---
I'm not particularly knowledgable about console issues. Is a blaknking interval
relevant in a post CR
On 2017-03-07 10:15, Christoph Hellwig wrote:
On Tue, Mar 07, 2017 at 09:50:22AM -0500, Austin S. Hemmelgarn wrote:
He's referring to the RAID mode most modern Intel chipsets have, which (last
I checked) Linux does not support completely and many OEM's are setting by
default on n
On 2017-03-06 23:52, Christoph Hellwig wrote:
On Sun, Mar 05, 2017 at 06:09:42PM -0800, David F. wrote:
More and more systems are coming with M2 on RAID and Linux doesn't
work unless you change the system out of RAID mode. This is becoming
more and more of a problem. What is the status of Lin
On 2017-01-31 10:29, Paul Menzel wrote:
Dear Borislav, dear Mario,
On 01/27/17 18:16, mario.limoncie...@dell.com wrote:
-Original Message-
From: Borislav Petkov [mailto:b...@alien8.de]
Sent: Friday, January 27, 2017 11:11 AM
To: Paul Menzel
Cc: Ashok Raj ; Linux Kernel Mailing List ;
On 2016-11-16 16:18, Mattias Nissler wrote:
I understand that silence suggests there's little interest, but here's
some new information I discovered today that may justify to reconsider
the patch:
The BSDs already have exactly what I propose, the mount option is
called "nosymfollow" there:
https
On 2016-11-09 21:29, Qu Wenruo wrote:
At 11/10/2016 06:57 AM, Andreas Dilger wrote:
On Nov 9, 2016, at 1:56 PM, Jaegeuk Kim wrote:
This patch implements multiple devices support for f2fs.
Given multiple devices by mkfs.f2fs, f2fs shows them entirely as one big
volume under one f2fs instance
On 2016-11-04 10:39, Markus Trippelsdorf wrote:
On 2016.11.04 at 15:24 +0100, Sebastian Andrzej Siewior wrote:
On 2016-11-04 07:37:02 [-0400], Austin S. Hemmelgarn wrote:
clued enough to have known better. Reassigning bug reports in question
from gcc-6 to linux is beyond stupid; Balint is
On 2016-11-04 10:24, Sebastian Andrzej Siewior wrote:
On 2016-11-04 07:37:02 [-0400], Austin S. Hemmelgarn wrote:
clued enough to have known better. Reassigning bug reports in question
from gcc-6 to linux is beyond stupid; Balint is either being deliberately
obtuse, or geniunely unable to
On 2016-11-03 21:08, Al Viro wrote:
On Thu, Nov 03, 2016 at 04:50:55PM -0600, Ben Hutchings wrote:
On Wed, 2016-11-02 at 18:20 +0100, Sebastian Andrzej Siewior wrote:
Debian started to build the gcc with -fPIE by default so the kernel
build ends before it starts properly with:
|kernel/bounds.c:
On 2016-10-17 09:02, Mattias Nissler wrote:
OK, no more feedback thus far. Is there generally any interest in a
mount option to avoid path name aliasing resulting in target file
confusion? Perhaps a version that only disables symlinks instead of
also hard-disabling files hard-linked to multiple l
On 2016-10-07 06:50, SF Markus Elfring wrote:
Linux has tons of issues, fixes for real problems are very welcome.
Is a spectrum of software improvements to reconsider there?
But coding style bike shedding is just a waste of time.
Why do various software developers bother about coding style
On 2016-10-06 11:05, Paolo Valente wrote:
Il giorno 06 ott 2016, alle ore 15:52, Austin S. Hemmelgarn
ha scritto:
On 2016-10-06 08:50, Paolo Valente wrote:
Il giorno 06 ott 2016, alle ore 13:57, Austin S. Hemmelgarn
ha scritto:
On 2016-10-06 07:03, Mark Brown wrote:
On Thu, Oct 06
On 2016-10-06 08:50, Paolo Valente wrote:
Il giorno 06 ott 2016, alle ore 13:57, Austin S. Hemmelgarn
ha scritto:
On 2016-10-06 07:03, Mark Brown wrote:
On Thu, Oct 06, 2016 at 10:04:41AM +0200, Linus Walleij wrote:
On Tue, Oct 4, 2016 at 9:14 PM, Tejun Heo wrote:
I get that bfq can
On 2016-10-06 07:03, Mark Brown wrote:
On Thu, Oct 06, 2016 at 10:04:41AM +0200, Linus Walleij wrote:
On Tue, Oct 4, 2016 at 9:14 PM, Tejun Heo wrote:
I get that bfq can be a good compromise on most desktop workloads and
behave reasonably well for some server workloads with the slice
expirat
On 2016-09-17 01:14, James Bottomley wrote:
On Fri, 2016-09-16 at 13:06 -0400, Austin S. Hemmelgarn wrote:
On 2016-09-16 12:21, James Bottomley wrote:
On Fri, 2016-09-16 at 11:53 -0400, Austin S. Hemmelgarn wrote:
On 2016-09-16 07:16, Hannes Reinecke wrote:
On 09/15/2016 10:52 PM, Jason A
On 2016-09-16 12:21, James Bottomley wrote:
On Fri, 2016-09-16 at 11:53 -0400, Austin S. Hemmelgarn wrote:
On 2016-09-16 07:16, Hannes Reinecke wrote:
On 09/15/2016 10:52 PM, Jason A. Donenfeld wrote:
Hi Martin,
On Thu, Sep 15, 2016 at 6:07 PM, Martin K. Petersen
But how do they signal that
On 2016-09-16 07:16, Hannes Reinecke wrote:
On 09/15/2016 10:52 PM, Jason A. Donenfeld wrote:
Hi Martin,
On Thu, Sep 15, 2016 at 6:07 PM, Martin K. Petersen
But how do they signal that ATA passthrough is possible? Is there an ATA
Information VPD page? Is REPORT SUPPORTED OPERATION CODES suppor
On 2016-09-12 02:55, Artem Bityutskiy wrote:
On Sun, 2016-09-11 at 15:04 +0200, Christoph Hellwig wrote:
Logfs was introduced to the kernel in 2009, and hasn't seen any non
drive-by changes since 2012, while having lots of unsolved issues
including the complete lack of error handling, with more
On 2016-09-09 18:57, Tejun Heo wrote:
Hello, again.
On Mon, Sep 05, 2016 at 10:37:55AM -0700, Andy Lutomirski wrote:
* It doesn't bring any practical benefits in terms of capability.
Userland can trivially handle the system-root and namespace-roots in
a symmetrical manner.
Your idea of "t
On 2016-09-06 20:55, Kent Overstreet wrote:
On Tue, Sep 06, 2016 at 11:46:28AM +0200, Harald Dunkel wrote:
Hi folks,
I am pretty hesitant replacing the rock-solid ext4 by bcachefs on my servers.
Meaning no offense, but surely I would prefer to have ext4 with a thin "SSD
caching layer" over a co
On 2016-08-13 15:30, Pavel Machek wrote:
Hi!
It seems that in v4.8-rc0, /dev/sdX got reordered, and now USB devices
are probed before SATA drivers. That is pretty anti-social. It
broke my boot on my primary machine, and unfortunately due to BIOS
problems (keyboard does not work when connected th
On 2016-08-02 06:33, Baole Ni wrote:
I find that the developers often just specified the numeric value
when calling a macro which is defined with a parameter for access permission.
As we know, these numeric value for access permission have had the
corresponding macro,
and that using macro can im
On 2016-07-15 16:54, H. Peter Anvin wrote:
On July 15, 2016 6:59:56 AM PDT, Peter Zijlstra wrote:
On Fri, Jul 15, 2016 at 01:52:48PM +, Topi Miettinen wrote:
On 07/15/16 12:43, Peter Zijlstra wrote:
On Fri, Jul 15, 2016 at 01:35:47PM +0300, Topi Miettinen wrote:
Hello,
There are many ba
On 2016-06-22 01:16, Stephan Mueller wrote:
Am Dienstag, 21. Juni 2016, 15:31:07 schrieb Austin S. Hemmelgarn:
Hi Austin,
Little data, interesting statement for results on 200+ systems including
all major CPU arches all showing information leading in the same
directions.
Let me try
On 2016-06-21 14:04, Stephan Mueller wrote:
Am Dienstag, 21. Juni 2016, 13:51:15 schrieb Austin S. Hemmelgarn:
6. You have a significant lack of data regarding embedded systems, which
is one of the two biggest segments of Linux's market share. You list no
results for any pre-ARMv6 sy
On 2016-06-21 09:19, Tomas Mraz wrote:
On Út, 2016-06-21 at 09:05 -0400, Austin S. Hemmelgarn wrote:
On 2016-06-20 14:32, Stephan Mueller wrote:
[1] http://www.chronox.de/jent/doc/CPU-Jitter-NPTRNG.pdf
Specific things I notice about this:
1. QEMU systems are reporting higher values than
On 2016-06-21 12:28, Stephan Mueller wrote:
Am Dienstag, 21. Juni 2016, 12:03:56 schrieb Austin S. Hemmelgarn:
Hi Austin,
On 2016-06-21 03:32, Stephan Mueller wrote:
Am Dienstag, 21. Juni 2016, 09:12:07 schrieb Nikos Mavrogiannopoulos:
Hi Nikos,
On Mon, Jun 20, 2016 at 5:43 PM, Stephan
On 2016-06-21 13:23, Stephan Mueller wrote:
Am Dienstag, 21. Juni 2016, 13:18:33 schrieb Austin S. Hemmelgarn:
Hi Austin,
You have to trust the host for anything, not just for the entropy in
timings. This is completely invalid argument unless you can present a
method that one guest can
On 2016-06-21 09:20, Stephan Mueller wrote:
Am Dienstag, 21. Juni 2016, 09:05:55 schrieb Austin S. Hemmelgarn:
Hi Austin,
On 2016-06-20 14:32, Stephan Mueller wrote:
Am Montag, 20. Juni 2016, 13:07:32 schrieb Austin S. Hemmelgarn:
Hi Austin,
On 2016-06-18 12:31, Stephan Mueller wrote:
Am
On 2016-06-21 09:42, Pavel Machek wrote:
Hi!
6. You have a significant lack of data regarding embedded systems, which is
one of the two biggest segments of Linux's market share. You list no
results for any pre-ARMv6 systems (Linux still runs on and is regularly used
on ARMv4 CPU's, and it's wo
On 2016-06-21 03:32, Stephan Mueller wrote:
Am Dienstag, 21. Juni 2016, 09:12:07 schrieb Nikos Mavrogiannopoulos:
Hi Nikos,
On Mon, Jun 20, 2016 at 5:43 PM, Stephan Mueller
wrote:
Personally, I don't really use /dev/random, nor would I recommend it
for most application programmers. At this
On 2016-06-20 14:32, Stephan Mueller wrote:
Am Montag, 20. Juni 2016, 13:07:32 schrieb Austin S. Hemmelgarn:
Hi Austin,
On 2016-06-18 12:31, Stephan Mueller wrote:
Am Samstag, 18. Juni 2016, 10:44:08 schrieb Theodore Ts'o:
Hi Theodore,
At the end of the day, with these devices you r
On 2016-06-18 10:45, Konstantin Khlebnikov wrote:
On Wed, Jun 15, 2016 at 5:47 PM, Austin S. Hemmelgarn
wrote:
On 2016-06-14 15:03, Konstantin Khlebnikov wrote:
I don't like the idea of this patchset.
All limitations are context dependent and that context changes rapidly.
You'll
On 2016-06-18 12:31, Stephan Mueller wrote:
Am Samstag, 18. Juni 2016, 10:44:08 schrieb Theodore Ts'o:
Hi Theodore,
At the end of the day, with these devices you really badly need a
hardware RNG. We can't generate randomness out of thin air. The only
thing you really can do requires user sp
On 2016-06-17 04:30, Vitaly Wool wrote:
Hi Minchan,
On Thu, Jun 16, 2016 at 1:17 AM, Minchan Kim wrote:
On Wed, Jun 15, 2016 at 10:42:07PM +0800, Geliang Tang wrote:
Change zram to use the zpool api instead of directly using zsmalloc.
The zpool api doesn't have zs_compact() and zs_pool_stats(
On 2016-06-14 15:03, Konstantin Khlebnikov wrote:
I don't like the idea of this patchset.
All limitations are context dependent and that context changes rapidly.
You'll never dump enough information for predicting future errors or
investigating reson of errors in past. You could try to reproduce
On 2016-06-12 20:18, Emese Revfy wrote:
On Sun, 12 Jun 2016 15:25:39 -0700
Kees Cook wrote:
I don't like this because it means if someone specifically selects
some plugins in their .config, and the headers are missing, the kernel
will successfully compile. For many plugins, this results in a k
On 2016-06-08 13:37, Guenter Roeck wrote:
On Wed, Jun 08, 2016 at 03:55:48PM +0200, Pali Rohár wrote:
On Wednesday 08 June 2016 15:24:10 Guenter Roeck wrote:
On 06/08/2016 02:57 AM, Pali Rohár wrote:
Hello!
Mario wrote me about two I think security problems in
dell-smm-hwmon driver and I woul
On 2016-06-04 21:36, Ken Moffat wrote:
On Sat, Jun 04, 2016 at 03:34:01PM -0400, Justin Keller wrote:
Correct the grammar around the word however.
Signed-off-by: Justin Keller
---
index 1d9bbab..5d43510 100644
--- a/Documentation/ntb.txt
+++ b/Documentation/ntb.txt
@@ -35,7 +35,7 @@ establis
On 2016-06-01 04:00, Boris wrote:
Hi Nicolai,
Yes, I think this is too ugly:
#!/usr/bin/gawk {exit system("/bin/sh -c 'exec \"$(dirname \"$0\")\"/subdir/catself
\"$0\"' " FILENAME);}
Imagine you have that feature in your kernel would you rather use:
#!{dirname}/subdir/catself
The problem wit
On 2016-06-01 03:48, Sergey Senozhatsky wrote:
On (06/01/16 15:47), Minchan Kim wrote:
[..]
so both BUILTIN and BUILT-AS-A-MODULE cases are handled at compile
time now and we can avoid crypto_has_comp() checks for most of the
comp_algorithm calls, except for the case when someone requests an
out
On 2016-05-18 11:19, Sebastian Frias wrote:
Hi Austin,
On 05/17/2016 07:29 PM, Austin S. Hemmelgarn wrote:
I see the difference, your answer seems a bit like the one from Austin,
basically:
- killing a process is a sort of kernel protection attempting to deal "automatically"
On 2016-05-17 12:16, Sebastian Frias wrote:
Hi Michal,
On 05/17/2016 10:57 AM, Michal Hocko wrote:
On Tue 17-05-16 10:24:20, Sebastian Frias wrote:
[...]
Also, under what conditions would copy-on-write fail?
When you have no memory or swap pages free and you touch a COW page that
is currentl
On 2016-05-13 11:37, Sebastian Frias wrote:
Hi Alan,
On 05/13/2016 05:04 PM, One Thousand Gnomes wrote:
Perhaps Sebastian's choice could be made to depend on CONFIG_EMBEDDED,
rather than CONFIG_EXPERT?
Even if the overcommit behavior is different on those systems the
primary question hasn't b
On 2016-05-13 10:35, Sebastian Frias wrote:
Hi Austin,
On 05/13/2016 03:51 PM, Austin S. Hemmelgarn wrote:
On 2016-05-13 09:32, Sebastian Frias wrote:
Well, it's hard to report, since it is essentially the result of a dynamic
system.
I could assume it killed terminals with a long hi
On 2016-05-13 10:23, Sebastian Frias wrote:
Hi Austin,
On 05/13/2016 04:14 PM, Austin S. Hemmelgarn wrote:
On 2016-05-13 09:34, Sebastian Frias wrote:
Hi Austin,
On 05/13/2016 03:11 PM, Austin S. Hemmelgarn wrote:
On 2016-05-13 08:39, Sebastian Frias wrote:
My point is that it seems to be
On 2016-05-13 09:34, Sebastian Frias wrote:
Hi Austin,
On 05/13/2016 03:11 PM, Austin S. Hemmelgarn wrote:
On 2016-05-13 08:39, Sebastian Frias wrote:
My point is that it seems to be possible to deal with such conditions in a more
controlled way, ie: a way that is less random and less
On 2016-05-13 09:32, Sebastian Frias wrote:
Hi Austin,
On 05/13/2016 03:11 PM, Austin S. Hemmelgarn wrote:
On 2016-05-13 08:39, Sebastian Frias wrote:
Well, a more urgent problem would be that in that case overcommit=never is not
really well tested.
I know more people who use overcommit
On 2016-05-13 06:18, Mason wrote:
On 13/05/2016 11:52, Michal Hocko wrote:
On Fri 13-05-16 10:44:30, Mason wrote:
On 13/05/2016 10:04, Michal Hocko wrote:
On Tue 10-05-16 13:56:30, Sebastian Frias wrote:
[...]
NOTE: I understand that the overcommit mode can be changed dynamically thru
sysctl
On 2016-05-13 08:39, Sebastian Frias wrote:
On 05/13/2016 02:00 PM, Michal Hocko wrote:
On Fri 13-05-16 11:52:30, Sebastian Frias wrote:
From what I remember, one of the LTP maintainers said that it is
highly unlikely people test (or run LTP for that matter) with
different settings for overcom
On 2016-05-03 09:57, Nikos Mavrogiannopoulos wrote:
On Tue, Apr 26, 2016 at 3:11 AM, Theodore Ts'o wrote:
On Mon, Apr 25, 2016 at 10:23:51AM +0200, Nikos Mavrogiannopoulos wrote:
That's far from a solution and I wouldn't recommend to anyone doing
that. We cannot expect each and every program t
On 2016-04-29 16:17, Jarkko Sakkinen wrote:
On Tue, Apr 26, 2016 at 09:00:10PM +0200, Pavel Machek wrote:
On Mon 2016-04-25 20:34:07, Jarkko Sakkinen wrote:
Intel(R) SGX is a set of CPU instructions that can be used by
applications to set aside private regions of code and data. The code
outsid
On 2016-04-27 02:00, Ard Biesheuvel wrote:
On 26 April 2016 at 22:34, Elliott, Robert (Persistent Memory)
wrote:
-Original Message-
From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel-
ow...@vger.kernel.org] On Behalf Of Davidlohr Bueso
Sent: Tuesday, April 26, 2016 1:34 PM
On 2016-04-26 15:47, Steven Rostedt wrote:
On Tue, 26 Apr 2016 20:44:58 +0200
Pavel Machek wrote:
I simply propose a way to let us kernel developers keep user space from
interfering, by adding a new kernel command line parameter that will
disable writing to /dev/kmsg. Any attempt to open the f
On 2016-04-26 14:10, Davidlohr Bueso wrote:
On Tue, 26 Apr 2016, Austin S. Hemmelgarn wrote:
At the absolute minimum, we should be logging (at least at a warning
level) that we had to fall back the the backup GPT. If somebody is
dealing with a disk that had a torn write to the primary GPT
On 2016-04-25 21:06, Julius Werner wrote:
The GUID Partiton Table layout maintains two synonymous partition tables
on a block device, one starting in sector 1 and one in the very last
sectors of the block device. This is useful if one of the tables gets
accidentally corrupted (e.g. through a part
On 2016-04-21 09:09, Anssi Hannula wrote:
Hi all!
Starting with commit b88a105802e9aeb [1] ("fat: mark fs as dirty on
mount and clean on umount") FAT(32) filesystems are now marked as
"dirty" on mount and clean on unmount.
The commit message says that this is similar to Win 7 behavior - "Win 7,
On 2016-04-19 23:27, Eric W. Biederman wrote:
"H. Peter Anvin" writes:
On April 19, 2016 12:25:03 PM PDT, "H. Peter Anvin" wrote:
Perhaps a (privileged) option to exempt from the global limit, then.
Something we can implement if asked for.
However, I wouldn't be 100% that the reserved pool
On 2016-03-21 13:29, Tycho Andersen wrote:
On Mon, Mar 21, 2016 at 11:22:06AM -0600, Chris Murphy wrote:
On Mon, Mar 21, 2016 at 9:21 AM, Tycho Andersen
wrote:
Hi all,
I'm seeing some strange behavior when bind mounting files from a btrfs
subvolume. Consider the output below:
root@criu2:/tmp
On 2016-03-11 15:24, Richard Weinberger wrote:
Am 11.03.2016 um 21:22 schrieb Cole:
If I remember correctly, when we were testing the fuse version, we hard coded
the path to see if that solved the problem, and the difference between
the env lookup
code and the hard coded path was almost the same
On 2016-03-11 11:20, Cole wrote:
Hi,
I have written a Variant Symlink Filesystem for linux, currently
implemented as a kernel module:
https://github.com/onslauth/varsymfs
The code was written for the 3.x kernel.
I would like to try to get this included into the linux kernel, and am
willing to h
On 2016-03-11 06:16, Christoph Hellwig wrote:
On Fri, Mar 04, 2016 at 01:10:31PM -0500, Austin S. Hemmelgarn wrote:
1. This all started long before blk-mq hit mainline.
Whoe cares? :)
It wasn't intended as an argument for this continuing to be developed
outside of blk-mq, but
On 2016-03-09 13:51, Colin Walters wrote:
On Wed, Mar 9, 2016, at 01:14 PM, Kees Cook wrote:
On Mon, Mar 7, 2016 at 9:15 PM, Andy Lutomirski wrote:
Hi all-
There are several users and distros that are nervous about user
namespaces from an attack surface point of view.
- RHEL and Arch have
On 2016-03-04 12:39, Christoph Hellwig wrote:
On Sat, Mar 05, 2016 at 12:29:39AM +0700, Linus Walleij wrote:
Hi Tejun,
I'm doing a summary of this discussion as a part of presenting
Linaro's involvement in Paolo's work. So I try to understand things.
Btw, can someone explain why you guys wast
On 2016-02-26 16:45, Al Viro wrote:
On Fri, Feb 26, 2016 at 10:36:50PM +0100, Stanislav Brabec wrote:
It should definitely report error whenever trying -oloop on top of
anything else than a file. Or at least a warning.
Well, even losetup should report a warning.
Keep in mind that with crypto
On 2016-02-26 15:30, Al Viro wrote:
On Fri, Feb 26, 2016 at 03:05:27PM -0500, Austin S. Hemmelgarn wrote:
Where is /mnt/2?
It's kind of interesting, but I can't reproduce _any_ of this
behavior with either ext4 or BTRFS when I manually set up the loop
devices and point mount(8
On 2016-02-26 14:12, Stanislav Brabec wrote:
Al Viro wrote:
On Fri, Feb 26, 2016 at 11:39:11AM -0500, Austin S. Hemmelgarn wrote:
That's just it though, from what I can tell based on what I've seen
and what you said above, mount(8) isn't doing things correctly in
this case. I
On 2016-02-26 12:07, Stanislav Brabec wrote:
Austin S. Hemmelgarn wrote:
> On 2016-02-26 10:50, Stanislav Brabec wrote:
That's just it though, from what I can tell based on what I've seen and
what you said above, mount(8) isn't doing things correctly in this case.
If we we
On 2016-02-26 10:50, Stanislav Brabec wrote:
Austin S. Hemmelgarn wrote:
> Added linux-btrfs as this should be documented there as a known issue
> until it gets fixed (although I have no idea which side is the issue).
This is a very bad behavior, as it makes impossible to safely use
Added linux-btrfs as this should be documented there as a known issue
until it gets fixed (although I have no idea which side is the issue).
On 2016-02-25 14:22, Stanislav Brabec wrote:
While writing a test suite for util-linux[1], I experienced a a strange
behavior of loop device:
When two loo
On 2016-02-22 11:18, Arnd Bergmann wrote:
On Monday 22 February 2016 16:56:53 Alexandre Belloni wrote:
One other workaround is to asked distributions
using systemd to stop using HCTOSYS so userspace would be responsible to
set the system time and in that case we won't have the 32/64 discrepancy.
On 2016-02-09 08:28, Christoph Hellwig wrote:
On Mon, Feb 08, 2016 at 03:28:35PM -0500, Nicolas Pitre wrote:
The config option to enable it all.
Just enable it by default..
I doubt we care too much about third party modules, but enabling this by
default will likely cause at least some of the
On 2016-01-28 03:56, Serge E. Hallyn wrote:
On Mon, Jan 25, 2016 at 10:57:32PM -0600, Eric W. Biederman wrote:
What sounds like a generally useful feature that would cover your use
case and many others is a per user limit on the number of user
namespaces users may create.
Ok, I'm sorry, but af
On 2016-01-27 05:27, Eric W. Biederman wrote:
Kees Cook writes:
On Tue, Jan 26, 2016 at 9:15 AM, Serge Hallyn wrote:
Quoting Josh Boyer (jwbo...@fedoraproject.org):
What you're saying is true for the "oh crap" case of a new userns
related CVE being found. However, there is the case where s
On 2016-01-26 14:56, Josh Boyer wrote:
On Tue, Jan 26, 2016 at 12:20 PM, Serge Hallyn wrote:
Quoting Josh Boyer (jwbo...@fedoraproject.org):
On Tue, Jan 26, 2016 at 9:46 AM, Austin S. Hemmelgarn
wrote:
On 2016-01-26 09:38, Josh Boyer wrote:
On Mon, Jan 25, 2016 at 11:57 PM, Eric W
On 2016-01-26 13:27, Andy Lutomirski wrote:
On Tue, Jan 26, 2016 at 10:09 AM, Austin S. Hemmelgarn
wrote:
On 2016-01-26 12:15, Serge Hallyn wrote:
Quoting Josh Boyer (jwbo...@fedoraproject.org):
On Mon, Jan 25, 2016 at 11:57 PM, Eric W. Biederman
wrote:
Kees Cook writes:
On Mon, Jan
On 2016-01-26 12:15, Serge Hallyn wrote:
Quoting Josh Boyer (jwbo...@fedoraproject.org):
On Mon, Jan 25, 2016 at 11:57 PM, Eric W. Biederman
wrote:
Kees Cook writes:
On Mon, Jan 25, 2016 at 11:33 AM, Eric W. Biederman
wrote:
Kees Cook writes:
Well, I don't know about less weird, but it
On 2016-01-26 09:38, Josh Boyer wrote:
On Mon, Jan 25, 2016 at 11:57 PM, Eric W. Biederman
wrote:
Kees Cook writes:
On Mon, Jan 25, 2016 at 11:33 AM, Eric W. Biederman
wrote:
Kees Cook writes:
Well, I don't know about less weird, but it would leave a unneeded
hole in the permission chec
On 2016-01-06 08:54, One Thousand Gnomes wrote:
In fact, there already appears to be some degree of allocation on demand
for VT's (otherwise deallocvt has no point), just not for everything
associated with the VT. I'd be willing to bet that almost everything
that reasonably can be dynamically al
On 2016-01-04 10:34, Pierre Paul MINGOT wrote:
> Hello,
>
> In Linux there is no way to set the number of tty devices or console
> to create. By default the kernel create 64 /dev/tty devices. what is
> too much for embedded system with limited resources. As all these 64
> devices are not necessary
1 - 100 of 325 matches
Mail list logo
