<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/fs/ncpfs, branch linux-4.4.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-4.4.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-4.4.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2019-03-23T07:44:21Z</updated>
<entry>
<title>ncpfs: fix build warning of strncpy</title>
<updated>2019-03-23T07:44:21Z</updated>
<author>
<name>Greg Kroah-Hartman</name>
</author>
<published>2019-03-07T16:02:50Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=eeb234f7f9079648f43e400bd0bfe84a8241a805'/>
<id>urn:sha1:eeb234f7f9079648f43e400bd0bfe84a8241a805</id>
<content type='text'>
Not upstream as ncpfs is long deleted.

Fix up two strncpy build warnings in ncp_get_charsets() by using strscpy
and the max size of the array.

It's not like anyone uses this code anyway, and this gets rid of two
build warnings so that we can see real warnings as they pop up over
time.

Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>staging: ncpfs: memory corruption in ncp_read_kernel()</title>
<updated>2018-03-28T16:40:15Z</updated>
<author>
<name>Dan Carpenter</name>
</author>
<published>2018-03-19T11:07:45Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=badf74b65fc27112f5fee871c7ade9199c74b2e1'/>
<id>urn:sha1:badf74b65fc27112f5fee871c7ade9199c74b2e1</id>
<content type='text'>
commit 4c41aa24baa4ed338241d05494f2c595c885af8f upstream.

If the server is malicious then *bytes_read could be larger than the
size of the "target" buffer.  It would lead to memory corruption when we
do the memcpy().

Reported-by: Dr Silvio Cesare of InfoSect &lt;Silvio Cesare &lt;silvio.cesare@gmail.com&gt;
Signed-off-by: Dan Carpenter &lt;dan.carpenter@oracle.com&gt;
Cc: stable &lt;stable@vger.kernel.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>ncpfs: fix unused variable warning</title>
<updated>2018-02-25T10:03:50Z</updated>
<author>
<name>Miklos Szeredi</name>
</author>
<published>2016-09-27T09:03:57Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=633c324b829e13005b12470da1b2d5d447030e82'/>
<id>urn:sha1:633c324b829e13005b12470da1b2d5d447030e82</id>
<content type='text'>
commit 9a232de4999666b2e8ea6775b2b0e3e4feb09b7a upstream.

Without CONFIG_NCPFS_NLS the following warning is seen:

fs/ncpfs/dir.c: In function 'ncp_hash_dentry':
fs/ncpfs/dir.c:136:23: warning: unused variable 'sb' [-Wunused-variable]
   struct super_block *sb = dentry-&gt;d_sb;

Signed-off-by: Miklos Szeredi &lt;mszeredi@redhat.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>ncpfs: fix a braino in OOM handling in ncp_fill_cache()</title>
<updated>2016-03-16T15:42:59Z</updated>
<author>
<name>Al Viro</name>
</author>
<published>2016-03-08T03:17:07Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=3c92cc68a18238456bda23678d96e91afd9a8f6c'/>
<id>urn:sha1:3c92cc68a18238456bda23678d96e91afd9a8f6c</id>
<content type='text'>
commit 803c00123a8012b3a283c0530910653973ef6d8f upstream.

Failing to allocate an inode for child means that cache for *parent* is
incompletely populated.  So it's parent directory inode ('dir') that
needs NCPI_DIR_CACHE flag removed, *not* the child inode ('inode', which
is what we'd failed to allocate in the first place).

Fucked-up-in: commit 5e993e25 ("ncpfs: get rid of d_validate() nonsense")
Fucked-up-by: Al Viro &lt;viro@zeniv.linux.org.uk&gt;
Signed-off-by: Al Viro &lt;viro@zeniv.linux.org.uk&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>ncpfs: don't allow negative timeouts</title>
<updated>2015-11-21T00:17:32Z</updated>
<author>
<name>Dan Carpenter</name>
</author>
<published>2015-11-20T23:56:56Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=1491e30ed1a741009d1d38f9285f7a29e6c05c78'/>
<id>urn:sha1:1491e30ed1a741009d1d38f9285f7a29e6c05c78</id>
<content type='text'>
This code causes a static checker warning because it's a user controlled
variable where we cap the upper bound but not the lower bound.  Let's
return an -EINVAL for negative timeouts.

[akpm@linux-foundation.org: remove unneeded `else']
Signed-off-by: Dan Carpenter &lt;dan.carpenter@oracle.com&gt;
Reviewed-by: Jan Kara &lt;jack@suse.com&gt;
Cc: Petr Vandrovec &lt;petr@vandrovec.name&gt;
Cc: David Howells &lt;dhowells@redhat.com&gt;
Cc: Jan Kara &lt;jack@suse.cz&gt;
Cc: Al Viro &lt;viro@zeniv.linux.org.uk&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>fs/ncpfs/dir.c: remove unnecessary new_valid_dev() check</title>
<updated>2015-11-09T23:11:24Z</updated>
<author>
<name>Yaowei Bai</name>
</author>
<published>2015-11-09T22:58:50Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=4467e29f0c48d0fc3e164c39c1eccd1ce230fbe4'/>
<id>urn:sha1:4467e29f0c48d0fc3e164c39c1eccd1ce230fbe4</id>
<content type='text'>
new_valid_dev() always returns 1, so the !new_valid_dev() check is not
needed.  Remove it.

Signed-off-by: Yaowei Bai &lt;bywxiaobai@163.com&gt;
Cc: Alexander Viro &lt;viro@zeniv.linux.org.uk&gt;
Cc: Petr Vandrovec &lt;petr@vandrovec.name&gt;
Cc: Jan Kara &lt;jack@suse.cz&gt;
Cc: Jens Axboe &lt;axboe@fb.com&gt;
Cc: Tejun Heo &lt;tj@kernel.org&gt;
Cc: Fabian Frederick &lt;fabf@skynet.be&gt;
Cc: David Howells &lt;dhowells@redhat.com&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>fs: Drop unlikely before IS_ERR(_OR_NULL)</title>
<updated>2015-09-29T13:13:58Z</updated>
<author>
<name>Viresh Kumar</name>
</author>
<published>2015-08-12T10:29:44Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=a1c83681d52704c766d576bea2d7f2f99e8dde23'/>
<id>urn:sha1:a1c83681d52704c766d576bea2d7f2f99e8dde23</id>
<content type='text'>
IS_ERR(_OR_NULL) already contain an 'unlikely' compiler flag and there
is no need to do that again from its callers. Drop it.

Signed-off-by: Viresh Kumar &lt;viresh.kumar@linaro.org&gt;
Reviewed-by: Jeff Layton &lt;jlayton@poochiereds.net&gt;
Reviewed-by: David Howells &lt;dhowells@redhat.com&gt;
Reviewed-by: Steve French &lt;smfrench@gmail.com&gt;
Signed-off-by: Jiri Kosina &lt;jkosina@suse.cz&gt;
</content>
</entry>
<entry>
<title>ncpfs: successful rename() should invalidate caches for parents</title>
<updated>2015-06-14T15:31:39Z</updated>
<author>
<name>Al Viro</name>
</author>
<published>2015-06-06T13:15:55Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=3f4a9494104cbadfa05cb2da9ca04b205712360f'/>
<id>urn:sha1:3f4a9494104cbadfa05cb2da9ca04b205712360f</id>
<content type='text'>
Signed-off-by: Al Viro &lt;viro@zeniv.linux.org.uk&gt;
</content>
</entry>
<entry>
<title>VFS: normal filesystems (and lustre): d_inode() annotations</title>
<updated>2015-04-15T19:06:57Z</updated>
<author>
<name>David Howells</name>
</author>
<published>2015-03-17T22:25:59Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=2b0143b5c986be1ce8408b3aadc4709e0a94429d'/>
<id>urn:sha1:2b0143b5c986be1ce8408b3aadc4709e0a94429d</id>
<content type='text'>
that's the bulk of filesystem drivers dealing with inodes of their own

Signed-off-by: David Howells &lt;dhowells@redhat.com&gt;
Signed-off-by: Al Viro &lt;viro@zeniv.linux.org.uk&gt;
</content>
</entry>
<entry>
<title>switch generic_write_checks() to iocb and iter</title>
<updated>2015-04-12T02:30:21Z</updated>
<author>
<name>Al Viro</name>
</author>
<published>2015-04-09T16:55:47Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=3309dd04cbcd2cdad168485af5cf3576b5051e49'/>
<id>urn:sha1:3309dd04cbcd2cdad168485af5cf3576b5051e49</id>
<content type='text'>
... returning -E... upon error and amount of data left in iter after
(possible) truncation upon success.  Note, that normal case gives
a non-zero (positive) return value, so any tests for != 0 _must_ be
updated.

Signed-off-by: Al Viro &lt;viro@zeniv.linux.org.uk&gt;

Conflicts:
	fs/ext4/file.c
</content>
</entry>
</feed>
