ilesystems/multigrain-ts.rst | 120
>
> 1 file changed, 120 insertions(+)
>
Reviewed-by: Randy Dunlap
Thanks.
--
~Randy
On 7/8/24 8:53 AM, Jeff Layton wrote:
> Add a high-level document that describes how multigrain timestamps work,
> rationale for them, and some info about implementation and tradeoffs.
>
> Signed-off-by: Jeff Layton
> ---
> Documentation/filesystems/multigrain-ts.rst | 120
>
On 7/5/24 10:02 AM, Jeff Layton wrote:
> Add a high-level document that describes how multigrain timestamps work,
> rationale for them, and some info about implementation and tradeoffs.
>
> Signed-off-by: Jeff Layton
> ---
> Documentation/filesystems/multigrain-ts.rst | 120
> +++
ce(struct ref_action *ra)
../fs/btrfs/ref-verify.c:225:1: warning: ‘inline’ is not at beginning of
declaration [-Wold-style-declaration]
static void inline __print_stack_trace(struct btrfs_fs_info *fs_info,
Fixes: fd708b81d972 ("Btrfs: add a extent ref verify tool")
Signed-off-by: Ran
On 2/4/19 10:12 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20190204:
>
on i386:
../fs/btrfs/zstd.c: In function ‘zstd_reclaim_timer_fn’:
../fs/btrfs/zstd.c:27:35: warning: integer overflow in expression [-Woverflow]
#define ZSTD_BTRFS_RECLAIM_NS (45 * NSEC_PER_SEC)
On 05/09/2018 09:01 AM, Eric Sandeen wrote:
> Move the btrfs label ioctls up to the vfs for general use.
>
> This retains 256 chars as the maximum size through the interface, which
> is the btrfs limit and AFAIK exceeds any other filesystem's maximum
> label size.
>
> Signed-off-by: Eric Sandeen
On 03/09/2018 04:07 PM, Andrew Morton wrote:
> On Fri, 9 Mar 2018 12:05:36 -0800 Kees Cook wrote:
>
>> When max() is used in stack array size calculations from literal values
>> (e.g. "char foo[max(sizeof(struct1), sizeof(struct2))]", the compiler
>> thinks this is a dynamic calculation due to th
On 12/15/2017 09:10 AM, Matthew Wilcox wrote:
> On Mon, Dec 11, 2017 at 03:10:22PM -0800, Randy Dunlap wrote:
>>> +The XArray does not support storing :c:func:`IS_ERR` pointers; some
>>> +conflict with data values and others conflict with entries the XArray
>>> +uses
On 12/15/2017 04:34 AM, Matthew Wilcox wrote:
> On Thu, Dec 14, 2017 at 08:22:14PM -0800, Matthew Wilcox wrote:
>> On Mon, Dec 11, 2017 at 03:10:22PM -0800, Randy Dunlap wrote:
>>>> +A freshly-initialised XArray contains a ``NULL`` pointer at every index.
>>>> +Eac
On 12/05/2017 04:40 PM, Matthew Wilcox wrote:
> From: Matthew Wilcox
>
> This is documentation on how to use the XArray, not details about its
> internal implementation.
>
> Signed-off-by: Matthew Wilcox
> ---
> Documentation/core-api/index.rst | 1 +
> Documentation/core-api/xarray.rst | 2
On 10/03/17 13:10, Dave Chinner wrote:
> On Tue, Oct 03, 2017 at 03:19:18PM +0200, Martin Steigerwald wrote:
>> [repost. I didn´t notice autocompletion gave me wrong address for fsdevel,
>> blacklisted now]
>>
>> Hello.
>>
>> What do you think of
>>
>> http://open-zfs.org/wiki/Projects/ZFS_Channel
On 04/07/17 08:08, Randy Dunlap wrote:
> On 04/07/17 01:27, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20170406:
>>
>
> on i386:
>
> ERROR: "__udivdi3" [fs/btrfs/btrfs.ko] undefined!
>
> Reported-by: Randy Du
On 04/07/17 01:27, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20170406:
>
on i386:
ERROR: "__udivdi3" [fs/btrfs/btrfs.ko] undefined!
Reported-by: Randy Dunlap
--
~Randy
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
On 04/29/16 00:13, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20160428:
>
on i386:
fs/built-in.o: In function `scrub_raid56_parity':
scrub.c:(.text+0x2d06fb): undefined reference to `__udivdi3'
--
~Randy
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
th
On 05/25/11 09:47, Steven Rostedt wrote:
> On Wed, 2011-05-25 at 09:12 -0700, Randy Dunlap wrote:
>>
>>> But what I sent out previously is not going into 2.6.40 anyway. Ingo
>>> feels that it's too late in the merge window to pull those changes and
>>>
On Wed, 25 May 2011 08:27:44 -0400 Steven Rostedt wrote:
> On Thu, 2011-05-26 at 01:49 -0400, liubo wrote:
> > On 05/01/2011 11:35 AM, Steven Rostedt wrote:
> > > On Fri, 2011-04-29 at 18:01 +0800, liubo wrote:
> > >> ping?
> > >
> > > Sorry, I've been trying to get the new ftrace function tracer
On Wed, 06 Apr 2011 17:18:46 +0800 liubo wrote:
>
> Btrfs has some "ULL" macros, and when these macros are passed to tracepoints'
> __print_symbolic(), there will be 64->32 truncate WARNINGS during compiling
> on 32bit box.
Hi,
Can this also be used to stop this warning that has been around
lik
ned
> int’, but argument 4 has type ‘sector_t’
>
> Hence always cast it to `unsigned long long' for printing.
>
> Introduced by commit e65e1535542931e51189832264cd282e5899e4b9 ("btrfs: fix
> panic caused by direct IO")
>
> Signed-off-by: Geert Uytterh
On Mon, 21 Jun 2010 16:18:39 -0700 Dan Magenheimer wrote:
> [PATCH V3 1/8] Cleancache: Documentation
>
> Add cleancache documentation to Documentation/vm and
> sysfs ABI documentation to Documentation/ABI
>
> Signed-off-by: Dan Magenheimer
>
> Diffstat:
> ABI/testing/sysfs-kernel-mm-cleancach
Theodore Tso wrote:
> On Wed, Jan 28, 2009 at 11:01:57AM -0500, Bill Nottingham wrote:
>> Bill Nottingham (nott...@redhat.com) said:
>>> btrfs requires version 0.18 of its tools, and squashfs requires
>>> 4.0.
>> This time, with a typo fix.
>
> While you're at it, could you also update e2fsprogs
20 matches
Mail list logo
