linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: syzbot+@syzkaller.appspotmail.com,
	syzkaller-bugs@googlegroups.com, dvyukov@google.com
Cc: ebiederm@xmission.com, linux-fsdevel@vger.kernel.org,
	linux-mm@kvack.org, netdev@vger.kernel.org,
	viro@zeniv.linux.org.uk
Subject: Re: WARNING: refcount bug in should_fail
Date: Sun, 1 Apr 2018 19:41:06 +0900	[thread overview]
Message-ID: <201804011941.IAE69652.OHMVJLFtSOFFQO@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <94eb2c0b816e88bfc50568c6fed5@google.com>

syzbot wrote:
> > On Sun, Mar 4, 2018 at 6:57 AM, Tetsuo Handa
> > <penguin-kernel@i-love.sakura.ne.jp> wrote:
> >> Switching from mm to fsdevel, for this report says that put_net(net) in
> >> rpc_kill_sb() made net->count < 0 when mount_ns() failed due to
> >> register_shrinker() failure.
> 
> >> Relevant commits will be
> >> commit 9ee332d99e4d5a97 ("sget(): handle failures of  
> >> register_shrinker()") and
> >> commit d91ee87d8d85a080 ("vfs: Pass data, ns, and ns->userns to  
> >> mount_ns.").
> 
> >> When sget_userns() in mount_ns() failed, mount_ns() returns an error  
> >> code to
> >> the caller without calling fill_super(). That is, get_net(sb->s_fs_info)  
> >> was
> >> not called by rpc_fill_super() (via fill_super callback passed to  
> >> mount_ns())
> >> but put_net(sb->s_fs_info) is called by rpc_kill_sb() (via fs->kill_sb()  
> >> from
> >> deactivate_locked_super()).
> 
> >> ----------
> >> static struct dentry *
> >> rpc_mount(struct file_system_type *fs_type,
> >>                  int flags, const char *dev_name, void *data)
> >> {
> >>          struct net *net = current->nsproxy->net_ns;
> >>          return mount_ns(fs_type, flags, data, net, net->user_ns,  
> >> rpc_fill_super);
> >> }
> >> ----------
> 
> > Messed kernel output, this is definitely not in should_fail.
> 
> > #syz dup: WARNING: refcount bug in sk_alloc
> 
> Can't find the corresponding bug.
> 
I don't think this is a dup of existing bug.
We need to fix either 9ee332d99e4d5a97 or d91ee87d8d85a080.

  reply	other threads:[~2018-04-01 10:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <001a113f6736499d1c0566363863@google.com>
2018-03-04  5:57 ` Tetsuo Handa
2018-04-01 10:32   ` Dmitry Vyukov
2018-04-01 10:32     ` syzbot
2018-04-01 10:41       ` Tetsuo Handa [this message]
2018-04-02 20:30         ` Eric W. Biederman
2018-04-02 21:52           ` Al Viro
2018-04-02 21:59             ` Al Viro
2018-04-03  5:20               ` Al Viro
2018-04-03 11:27                 ` Dmitry Vyukov
2018-04-04 15:54                 ` Eric W. Biederman
2018-04-21 10:26                   ` Tetsuo Handa
2018-04-01 10:37     ` Dmitry Vyukov
2018-04-01 11:11       ` Tetsuo Handa
2018-04-01 11:30         ` Dmitry Vyukov
2018-04-01 11:46           ` Dmitry Vyukov
2018-04-01 11:50             ` Dmitry Vyukov

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=201804011941.IAE69652.OHMVJLFtSOFFQO@I-love.SAKURA.ne.jp \
    --to=penguin-kernel@i-love.sakura.ne.jp \
    --cc=dvyukov@google.com \
    --cc=ebiederm@xmission.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=netdev@vger.kernel.org \
    --cc=syzbot+@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=viro@zeniv.linux.org.uk \
    --subject='Re: WARNING: refcount bug in should_fail' \
    /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

This is a public inbox, see mirroring instructions
on how to clone and mirror all data and code used for this inbox