Hi,
We're noticing a rare race here with open() in tail(1), where this happens:
tail --follow=name "file"
/* "file" is unlinked() by another process */
read(IN_ATTRIB from inotify); /* for st_nlink-- */
open("file") /* Done to check if deleted, but this succeeds! */
The open() succ
On 07/09/15 10:52, Pádraig Brady wrote:
> On 07/09/15 07:46, Naoya Horiguchi wrote:
>> On Mon, Sep 07, 2015 at 02:23:44AM +, Horiguchi Naoya(堀口 直也) wrote:
>>> On Mon, Sep 07, 2015 at 02:29:53AM +0100, Pádraig Brady wrote:
>>>> On 20/08/15 09:26, Naoya Horiguchi wr
On 07/09/15 07:46, Naoya Horiguchi wrote:
> On Mon, Sep 07, 2015 at 02:23:44AM +, Horiguchi Naoya(堀口 直也) wrote:
>> On Mon, Sep 07, 2015 at 02:29:53AM +0100, Pádraig Brady wrote:
>>> On 20/08/15 09:26, Naoya Horiguchi wrote:
>>>> Currently /proc/PID/smaps
On 20/08/15 09:26, Naoya Horiguchi wrote:
> Currently /proc/PID/smaps provides no usage info for vma(VM_HUGETLB), which
> is inconvenient when we want to know per-task or per-vma base hugetlb usage.
> To solve this, this patch adds a new line for hugetlb usage like below:
>
> Size:
On 04/08/15 03:13, Guenter Roeck wrote:
> The watchdog infrastructure is currently purely passive, meaning
> it only passes information from user space to drivers and vice versa.
>
> Since watchdog hardware tends to have its own quirks, this can result
> in quite complex watchdog drivers. A number
On 10/05/15 14:26, Alexey Dobriyan wrote:
> On Sat, May 09, 2015 at 06:07:18AM +0100, Pádraig Brady wrote:
>> On 08/05/15 14:26, Alexey Dobriyan wrote:
>
>>> exuberant()
>>> {
>>> - all_target_sources | xargs $1 -a
On 08/05/15 14:26, Alexey Dobriyan wrote:
> ctags is single-threaded program. Split list of files to be tagged into
> equal parts, 1 part for each CPU and then merge the results.
>
> Speedup on one 2-way box I have is ~143 s => ~99 s (-31%).
> On another 4-way box: ~120 s => ~65 s (-46%!).
>
> Re
On 31/03/15 01:48, Namhyung Kim wrote:
> Hi Steve,
>
> On Mon, Mar 30, 2015 at 05:15:11PM -0400, Steven Rostedt wrote:
>> On Thu, 26 Mar 2015 09:32:23 +0900
>> Namhyung Kim wrote:
>>
>>> The usleep is only provided on distros from Redhat so running ftracetest
>>> on other distro resulted in failu
On 25/03/15 18:57, Steven Rostedt wrote:
> On Wed, 25 Mar 2015 17:36:34 +
> Luis Henriques wrote:
>
>> 'usleep' seems to be a distro-specific utility and may not be
>> available:
>>
>> [5] event tracing - enable/disable with event level files [FAIL]
>> execute:
>> /home/miguel/linux/
Since fsync(), fdatasync(), syncfs() work on an identifying descriptor,
and all work against a read-only file for example,
should any/all these functions work with a descriptor opened with O_PATH ?
thanks,
Pádraig.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the b
On 24/01/15 12:29, Alexander Holler wrote:
> Am 24.01.2015 um 13:09 schrieb Alexander Holler:
>> Am 24.01.2015 um 12:37 schrieb Alexander Holler:
>>> Am 24.01.2015 um 11:45 schrieb Alexander Holler:
>>>
It uses shred, in the hope it will somedays learn how to shred stuff on
FLASH based de
On 24/01/15 00:13, Alexander Holler wrote:
> Am 24.01.2015 um 00:58 schrieb David Howells:
>> Alexander Holler wrote:
>>
>>> This is for the more paranoid people, also it's
>>> questionable what paranoid nowadays means.
>>
>> shred?
>
> Seems to do the same like when using dd, just that it does i
On 11/05/2014 11:13 PM, Martin Tournoij wrote:
> On Wed, Nov 5, 2014, at 20:31, Austin S Hemmelgarn wrote:
>> The people to talk to about that for the core
>> utilities on Linux would be the maintainers of the GNU coreutils, or
>> whatever your distribution might use in their place (I think it's
I noticed that nanosleep() on 64 bit, "only" supports 292 years,
rather than the full potential 292 billion years with 64 bit time_t, due to:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/include/linux/time.h?id=refs/tags/v3.16#n87
Attached is a program from Paul Eggert that
On 10/02/2014 08:52 AM, Yann Droneaud wrote:
> In order to not potentially break applications which were
> requesting O_CLOEXEC on event file descriptors but which
> actually need it to be not effective as the kernel currently
> ignore the flag, so the file descriptor is inherited accross
> exec re
On 04/03/2014 06:57 PM, Dave Reisner wrote:
> Hi,
>
> [This is a repost of a G+ post at Tejun's request]
>
> With Linux 3.14, you might notice in /proc/self/mountinfo that your
> root's parent FSID is now 0, instead of the 1 that it's been for the
> last N years. Tejun wrote the change (9e30cc959
On 03/20/2014 09:39 AM, Janani Venkataraman wrote:
> Hi all,
>
> The following series implements an infrastructure for capturing the core of an
> application without disrupting its process.
>
> Kernel Space Approach:
>
> 1) Posted an RFD to LKML explaining the various kernel-methods being analys
On 10/08/2013 10:02 AM, Ingo Molnar wrote:
> +ifeq ($(JOBS),)
> + JOBS := $(shell grep -c ^processor /proc/cpuinfo 2>/dev/null)
nproc is probably ubiquitous enough to use now
(available since coreutils 8.1 (end of 2009))
As well as being more concise, it will take
account of offline CPUs etc.
>
On 09/29/2013 08:14 AM, Richard Weinberger wrote:
> On Sun, Sep 29, 2013 at 7:22 AM, Pádraig Brady wrote:
>> On 09/25/2013 03:37 PM, richard -rw- weinberger wrote:
>>> On Wed, Sep 25, 2013 at 4:28 PM, Thomas Meyer wrote:
>>>> Am Mittwoch, den 25.09.2013, 08:59 -0500
On 09/25/2013 03:37 PM, richard -rw- weinberger wrote:
> On Wed, Sep 25, 2013 at 4:28 PM, Thomas Meyer wrote:
>> Am Mittwoch, den 25.09.2013, 08:59 -0500 schrieb Rob Landley:
>>> On 09/24/2013 01:36:56 PM, Thomas Meyer wrote:
Hi,
Is there such a thing?
>>>
>>> In the kernel's vfs la
On 05/15/2013 11:03 PM, Al Viro wrote:
> On Wed, May 15, 2013 at 01:38:48PM +0100, P??draig Brady wrote:
In today's Austin Group meeting, I was tasked to open a new bug that
would state specifically how the empty symlink is resolved; the intent
is to allow both Solaris behavior (curr
On 05/15/2013 03:40 PM, Eric Blake wrote:
> On 05/15/2013 06:38 AM, Pádraig Brady wrote:
>> On 01/17/2013 04:22 PM, Pádraig Brady wrote:
>>> On 01/17/2013 01:03 PM, Pádraig Brady wrote:
>>>> The discussion leading to this is at http://bugs.gnu.org/13447
>>>&g
On 01/17/2013 04:22 PM, Pádraig Brady wrote:
> On 01/17/2013 01:03 PM, Pádraig Brady wrote:
>> The discussion leading to this is at http://bugs.gnu.org/13447
>> In summary other systems allow an empty target for a symlink,
>> and POSIX specifies that it should be allowed?
>
On 03/30/2013 08:08 PM, Andreas Dilger wrote:
> On 2013-03-30, at 12:49 PM, Pavel Machek wrote:
>> Hmm, really? AFAICT it would be simple to provide an
>> open_deleted_file("directory") syscall. You'd open_deleted_file(),
>> copy source file into it, then fsync(), then link it into filesystem.
>>
>
On 03/25/2013 04:15 AM, Tony Chung wrote:
> The current maximum of 255 seconds is insufficient.
> For example, crash dump could take 5+ minutes.
>
> Signed-off-by: Tony Chung
> ---
> drivers/watchdog/w83627hf_wdt.c | 73 ++
> 1 files changed, 57 insertions(+
On 03/19/2013 08:02 PM, Guenter Roeck wrote:
> On Tue, Mar 19, 2013 at 05:26:26PM +0000, Pádraig Brady wrote:
>> On 03/10/2013 11:14 PM, Guenter Roeck wrote:
>>> It is unnecessary to enable the logical device and WDT0 each time
>>> the watchdog is accessed. Do it only
On 03/10/2013 11:14 PM, Guenter Roeck wrote:
> It is unnecessary to enable the logical device and WDT0 each time
> the watchdog is accessed. Do it only once during initialization.
Is this also the case on systems where the superio
chip is used for other things? I've the impression
that this may br
On 03/08/2013 11:21 PM, Jiri Slaby wrote:
> On 03/08/2013 07:42 AM, Hillf Danton wrote:
>> On Fri, Mar 8, 2013 at 3:37 AM, Jiri Slaby wrote:
>>> On 03/01/2013 03:02 PM, Hillf Danton wrote:
On Fri, Mar 1, 2013 at 1:02 AM, Jiri Slaby wrote:
>
> Ok, no difference, kswap is still crazy.
On 01/17/2013 01:03 PM, Pádraig Brady wrote:
The discussion leading to this is at http://bugs.gnu.org/13447
In summary other systems allow an empty target for a symlink,
and POSIX specifies that it should be allowed?
In relation to this, Eric Blake said:
> In today's Austin Group me
POSIX only states that ENOENT should be returned
if an empty string is specified for the link name.
In fact it states the link target...
"shall be treated only as a character string and
shall not be validated as a pathname".
Signed-off-by: Pádraig Brady
---
fs/namei.c |3 ++
On 12/12/2012 06:29 PM, Andy Lutomirski wrote:
On Sat, Dec 8, 2012 at 3:57 PM, Andy Lutomirski wrote:
I just tried to search to find actual uses of pI/fI. Here's what I found:
I downloaded all the Fedora spec files and searched for file
capabilities. Assuming I didn't mess up, here's what
On 10/30/2012 06:54 PM, Theodore Ts'o wrote:
On Tue, Oct 30, 2012 at 04:55:22PM +0200, Lasse Kärkkäinen wrote:
Apparently there has been little or no development on urandom even
though the device is in widespread use for disk shredding and such
use. The device emits data at rather slow rate of 1
On 10/21/2012 05:18 AM, abhishek agarwal wrote:
perfmon had "timeout" option and i guess, same do oprofile.
On Sat, Oct 20, 2012 at 1:58 AM, Pádraig Brady wrote:
On 10/13/2012 08:54 AM, abhishek agarwal wrote:
Hi folks..
I was thinking that why cant we have a timeout option in
On 10/13/2012 08:54 AM, abhishek agarwal wrote:
Hi folks..
I was thinking that why cant we have a timeout option in perf stat
command. The timeout feature will help us to profile a process for a
stipulated time (preferably in millisecs) and make perf stat return
after that time.
Eg:
perf stat
On 09/07/2012 01:48 PM, Jeff Layton wrote:
On Fri, 7 Sep 2012 08:34:53 -0400
Jeff Layton wrote:
Signed-off-by: Jeff Layton
---
fs/proc/base.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/fs/proc/base.c b/fs/proc/base.c
index 1b6c84c..58e801b 100644
--- a/fs/proc
On 07/26/2012 03:30 PM, Jidong Xiao wrote:
> Hi,
>
> I just have a simple question about fallocate.
>
> I want to test the punch hole function of fallocate(). So I wrote such
> a simple program:
>
> yosemite:/mnt # cat test.c
> #include
> #include
> #include
> #include
> #include
> #include
Ravinandan Arakali (rarakali) wrote:
> Hi Vaidy,
> What do you think is the right way to get the memory usage of a
> process, I mean the actual physical memory used ? Basically,
> I'm interested in the incremental cost of a process, which
> means, I don't want to include the text segments of shared
Alberto Gonzalez wrote:
> Hi,
>
> Maybe some of you have been hearing lately about a problem with laptop's hard
> disk drives being killed by *insert Linux distro here* [1]
I asked about this on the fedora devel list:
http://www.redhat.com/archives/fedora-devel-list/2007-October/msg02324.html
I
Adrian Bunk wrote:
> On Thu, Oct 25, 2007 at 09:12:45PM +0100, Michael Lothian wrote:
>>> The MPENTIUM4 option does not only set -march=pentium4, it also enables
>>> several other options in arch/i386/Kconfig.cpu resulting in better
>>> performance.
>> How about an autodetect to set the right optio
Ravinandan Arakali (rarakali) wrote:
> Hi kernel gurus,
> I am trying to find out the memory that's used on my linux box.
> I find that there are quite a few confusing metrics. How do
> I find out the "true" used memory ?
>
> 1. For eg. "free -m" shows free memory (excluding buffers/caches)
> as
Aidan Thornton wrote:
> I looked at this recently, and I'm not sure the core em28xx code was
> really that different (at least, pre-userspace). Most of the core
> changes seemed to be related to Markus' driver having (semi-working)
> VBI support. I haven't tried this recently; I disabled it a while
Matt LaPlante wrote:
> Since everyone loves random statistics, here are a few gems to give you a
> break from your busy day:
>
> Number of lines in the 2.6.22 Linux kernel source that include one or more
> trailing whitespaces: 135209
> Bytes saved by removing said whitespace: 151809
> Lines in
Vladislav Bolkhovitin wrote:
>
> I would also suggest one more feature: support for block level
> de-duplication. I mean:
>
> 1. Ability for Btrfs to have blocks in several files to point to the
> same block on disk
>
> 2. Support for new syscall or IOCTL to de-duplicate as a single
> transactio
H. Peter Anvin wrote:
> Eric Dumazet wrote:
>> As I said, this new non blocking feature on the input side (disk), is
>> nice and usefull. (For people scared by splice() syscall :) )
>>
>> Just have to mention it is a change of behavior, and documentation
>> probably needs to reflect this change. "S
William Lee Irwin III wrote:
> Any chance we can get some kind of devices set up for partitions of
> loop devices if we're going to redo loopdev setup? That's been a thorn
> in my side for some time.
This script might be of use:
http://www.pixelbeat.org/scripts/lomount.sh
cheers,
Pádraig.
-
To un
Andrew Morton wrote:
> On Tue, 06 Mar 2007 12:10:49 +
> P__draig Brady <[EMAIL PROTECTED]> wrote:
>> Perhaps one could possibly just evict pages with _mapcount==0 ?
>
> That is the present fadvise(FADV_DONTNEED) behaviour.
Ah right. It doesn't invalidate page_mapped() pages.
If that means it
Andrew Morton wrote:
> Yes. Let's flesh it out the backup program policy some more:
>
> - Unconditionally invalidate output files
>
> - on entry to read(), probe pagecache, record which pages in the range are
> present
>
> - on entry to next read(), shoot down those pages from the previous rea
Andrew Morton wrote:
> I've uploaded to http://userweb.kernel.org/~akpm/pagecache-management/ a
> little tool which permits the management of the pagecache usage of
> arbitrary applications. Effectively it prevents the targetted application
> from using any pagecache at all.
Cool, Kinda like noca
Arjan van de Ven wrote:
> sched_setaffinity takes 3 not 2 parameters.
Yep the interface changed 3 times, hence
it's probably better using the syscall directly.
Search my notes for sched_setaffinity here:
http://www.pixelbeat.org/programming/c_c++_notes.html
Pádraig.
-
To unsubscribe from this lis
Frank van Maarseveen wrote:
> On Tue, Jan 09, 2007 at 11:26:25AM -0500, Steven Rostedt wrote:
>> On Mon, 2007-01-08 at 13:00 +0100, Miklos Szeredi wrote:
>>
50% probability of false positive on 4G files seems like very ugly
design problem to me.
>>> 4 billion files, each with more than on
50 matches
Mail list logo
