On 2023/5/18 08:32, Jaegeuk Kim wrote:
On 05/17, Wu Bo wrote:
On 2023/5/17 16:36, Chao Yu wrote:
On 2023/5/17 11:59, Wu Bo wrote:
On 2023/5/17 10:44, Chao Yu wrote:
On 2023/5/16 20:07, Wu Bo wrote:
Modify the order between 'trace_f2fs_iget' &
'unlock_new_inode', so the
I_NEW can pass to the
On 05/17, Wu Bo wrote:
> On 2023/5/17 16:36, Chao Yu wrote:
> > On 2023/5/17 11:59, Wu Bo wrote:
> > > On 2023/5/17 10:44, Chao Yu wrote:
> > > > On 2023/5/16 20:07, Wu Bo wrote:
> > > > > Modify the order between 'trace_f2fs_iget' &
> > > > > 'unlock_new_inode', so the
> > > > > I_NEW can pass to
On 2023/5/17 16:36, Chao Yu wrote:
On 2023/5/17 11:59, Wu Bo wrote:
On 2023/5/17 10:44, Chao Yu wrote:
On 2023/5/16 20:07, Wu Bo wrote:
Modify the order between 'trace_f2fs_iget' & 'unlock_new_inode', so
the
I_NEW can pass to the trace event when the inode initialised.
Why is it needed?
On 2023/5/17 11:59, Wu Bo wrote:
On 2023/5/17 10:44, Chao Yu wrote:
On 2023/5/16 20:07, Wu Bo wrote:
Modify the order between 'trace_f2fs_iget' & 'unlock_new_inode', so the
I_NEW can pass to the trace event when the inode initialised.
Why is it needed? And trace_f2fs_iget() won't print
On 2023/5/17 10:44, Chao Yu wrote:
> On 2023/5/16 20:07, Wu Bo wrote:
>> Modify the order between 'trace_f2fs_iget' & 'unlock_new_inode', so the
>> I_NEW can pass to the trace event when the inode initialised.
>
> Why is it needed? And trace_f2fs_iget() won't print inode->i_state?
When connect a
On 2023/5/16 20:07, Wu Bo wrote:
Modify the order between 'trace_f2fs_iget' & 'unlock_new_inode', so the
I_NEW can pass to the trace event when the inode initialised.
Why is it needed? And trace_f2fs_iget() won't print inode->i_state?
Thanks,
Signed-off-by: Wu Bo
---
fs/f2fs/inode.c | 2
Modify the order between 'trace_f2fs_iget' & 'unlock_new_inode', so the
I_NEW can pass to the trace event when the inode initialised.
Signed-off-by: Wu Bo
---
fs/f2fs/inode.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/f2fs/inode.c b/fs/f2fs/inode.c
index
