* Re: [PATCH] Don't block writes to swap-files with ETXTBSY.
2021-08-27 15:16 ` [PATCH] Don't block writes to swap-files with ETXTBSY Christoph Hellwig
@ 2021-08-27 23:10 ` NeilBrown
2021-08-28 7:10 ` Christoph Hellwig
2021-09-02 4:19 ` Wang Yugui
1 sibling, 1 reply; 4+ messages in thread
From: NeilBrown @ 2021-08-27 23:10 UTC (permalink / raw)
To: Christoph Hellwig
Cc: Darrick J. Wong, Christoph Hellwig, David Howells, torvalds,
trond.myklebust, linux-nfs, linux-mm, linux-fsdevel, linux-kernel
On Sat, 28 Aug 2021, Christoph Hellwig wrote:
> On Thu, Aug 26, 2021 at 09:57:39AM +1000, NeilBrown wrote:
> >
> > Commit dc617f29dbe5 ("vfs: don't allow writes to swap files")
> > broke swap-over-NFS as it introduced an ETXTBSY error when NFS tries to
> > swap-out using ->direct_IO().
> >
> > There is no sound justification for this error. File permissions are
> > sufficient to stop non-root users from writing to a swap file, and root
> > must always be cautious not to do anything dangerous.
> >
> > These checks effectively provide a mandatory write lock on swap, and
> > mandatory locks are not supported in Linux.
> >
> > So remove all the checks that return ETXTBSY when attempts are made to
> > write to swap.
>
> Swap files are not just any files and do need a mandatory write lock
> as they are part of the kernel VM and writing to them will mess up
> the kernel badly. David Howells actually has sent various patches
> to fix swap over NFS in the last weeks.
>
>
There are lots of different things root can do which will mess up the
kernel badly. The backing-store can still be changed through some other
means.
Do you have a particular threat or risk scenario other than "root might
get careless"?
Yes, I've seen David's patches. I posted this one because I think the
original patch which broke swap-over-NFS was not just unfortunate, but
wrong. Permissions are how we protect files, not ETXTBSY.
NeilBrown
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: [PATCH] Don't block writes to swap-files with ETXTBSY.
2021-08-27 15:16 ` [PATCH] Don't block writes to swap-files with ETXTBSY Christoph Hellwig
2021-08-27 23:10 ` NeilBrown
@ 2021-09-02 4:19 ` Wang Yugui
1 sibling, 0 replies; 4+ messages in thread
From: Wang Yugui @ 2021-09-02 4:19 UTC (permalink / raw)
To: Christoph Hellwig
Cc: NeilBrown, Darrick J. Wong, David Howells, trond.myklebust,
linux-nfs
Hi,
# drop torvalds@linux-foundation.org, linux-mm@kvack.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
A Question about ETXTBSY of nfs.
# I tried google/bing, but yet no good info is found.
test case:
/ssd is a nfs directory
kernel: 5.10.61, 5.4.106 and more
1, on Node1:
[root@T630 ~]# echo -e '#!/bin/bash\necho hello' >/ssd/a.sh
[root@T630 ~]# chmod a+x /ssd/a.sh
2, on Node2:
[root@T640 ~]# /ssd/a.sh
-bash: /ssd/a.sh: /bin/bash: bad interpreter: Text file busy
[root@T640 ~]# bash /ssd/a.sh
hello
[root@T640 ~]# /ssd/a.sh
-bash: /ssd/a.sh: /bin/bash: bad interpreter: Text file busy
Is there any way(flush, sync) to avoid this ETXTBSY error(Text file busy)?
Best Regards
Wang Yugui (wangyugui@e16-tech.com)
2021/09/02
> On Thu, Aug 26, 2021 at 09:57:39AM +1000, NeilBrown wrote:
> >
> > Commit dc617f29dbe5 ("vfs: don't allow writes to swap files")
> > broke swap-over-NFS as it introduced an ETXTBSY error when NFS tries to
> > swap-out using ->direct_IO().
> >
> > There is no sound justification for this error. File permissions are
> > sufficient to stop non-root users from writing to a swap file, and root
> > must always be cautious not to do anything dangerous.
> >
> > These checks effectively provide a mandatory write lock on swap, and
> > mandatory locks are not supported in Linux.
> >
> > So remove all the checks that return ETXTBSY when attempts are made to
> > write to swap.
>
> Swap files are not just any files and do need a mandatory write lock
> as they are part of the kernel VM and writing to them will mess up
> the kernel badly. David Howells actually has sent various patches
> to fix swap over NFS in the last weeks.
^ permalink raw reply [flat|nested] 4+ messages in thread