Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Rohith Surabattula <rohiths.msft@gmail.com>
Cc: dhowells@redhat.com, Steve French <smfrench@gmail.com>,
	Shyam Prasad N <nspmangalore@gmail.com>,
	ronnie sahlberg <ronniesahlberg@gmail.com>,
	Paulo Alcantara <pc@cjr.nz>,
	jlayton@kernel.org, linux-cifs@vger.kernel.org
Subject: Re: cifs conversion to netfslib
Date: Thu, 17 Mar 2022 00:07:20 +0000	[thread overview]
Message-ID: <4085703.1647475640@warthog.procyon.org.uk> (raw)
In-Reply-To: <CACdtm0YuO+t46wQf9pKu9-U-=vguvwpEu6VXrkXV3JDocFM2qg@mail.gmail.com>

Rohith Surabattula <rohiths.msft@gmail.com> wrote:

> I noticed 2 other issues while running xfstests.
> 
> Noticed kernel OOPS during test generic/286:
> folio_test_writeback returned false which means PG_writeback flag has
> been cleared. I am not sure whether head page has PG_writeback flag
> set initially? Can you please confirm.
> 
> [ 2275.941096] CIFS: bad 2000 @64f0000 page 64f0 64f1
> [ 2275.945785] ------------[ cut here ]------------
> [ 2275.945787] kernel BUG at /home/lxsmbadmin/latest_14mar/linux-fs/fs/cifs/cifssmb.c:1954!
> ...
> [ 2275.969812] Workqueue: cifsiod cifs_writev_complete [cifs]
> [ 2275.974909] RIP: 0010:cifs_pages_written_back+0x1e1/0x1f0 [cifs]
> [ 2275.975570] CIFS: bad 2000 @64f0000 page 64f0 64f1
> [ 2275.980641] Call Trace:
> [ 2275.980643]  <TASK>
> [ 2275.980648]  cifs_writev_complete+0x43d/0x500 [cifs]

I don't see that, but it fails in some other ways.  I think the bits should be
set.

I am seeing the occasional:

	CIFS: trying to dequeue a deleted mid

but I haven't managed to work out how I get to that yet.

I'm also occasionally seeing cifs_open() return a number >0, which causes all
sorts of fun. 

> Noticed that with netfs integration, file open with O_DIRECT flag is
> not supported.

It should be.  It jumps off to netfs_direct_read_iter() in various places.

openat(AT_FDCWD, "/xfstest.test/hello2", O_RDWR|O_DIRECT) = 3
fstatfs(3, {f_type=SMB2_MAGIC_NUMBER, f_bsize=1024, f_blocks=54961016, f_bfree=23691924, f_bavail=23691924, f_files=0, f_ffree=0, f_fsid={val=[1904023890, 0]}, f_namelen=255, f_frsize=1024, f_flags=ST_VALID|ST_RELATIME}) = 0
fstat(3, {st_mode=S_IFREG|0755, st_size=278528, ...}) = 0
pread64(3, "\253\253\253\253\253\253\253\253\253\253\253\253\253\253\253\253\253\253\253\253\253\253\253\253\253\253\253\253\253\253\253\253"..., 4096, 0) = 4096

Btw, I've pushed an update to my cifs-experimental branch.

David


  reply	other threads:[~2022-03-17  0:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-11  8:19 cifs conversion to netfslib David Howells
2022-03-11  8:25 ` David Howells
2022-03-15  3:50   ` Rohith Surabattula
2022-03-15  9:54     ` Rohith Surabattula
2022-03-17  0:07       ` David Howells [this message]
2022-03-17 16:16         ` David Howells
2022-03-18  0:21         ` David Howells
2022-03-18  2:52           ` Steve French
2022-03-21 10:19             ` Rohith Surabattula
2022-03-21 17:18               ` David Howells

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4085703.1647475640@warthog.procyon.org.uk \
    --to=dhowells@redhat.com \
    --cc=jlayton@kernel.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=nspmangalore@gmail.com \
    --cc=pc@cjr.nz \
    --cc=rohiths.msft@gmail.com \
    --cc=ronniesahlberg@gmail.com \
    --cc=smfrench@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox