On Tue 21-01-25 15:10:48, libaokun@xxxxxxxxxxxxxxx wrote: > From: Baokun Li <libaokun1@xxxxxxxxxx> > > We now print error messages in ext4_end_bio() when page writeback > encounters an error. If data_err=abort is set, the journal will also > be aborted in a kworker. This means that we now check all Buffer I/O > in all modes and decide whether to abort the journal based on the > data_err option. Therefore, we remove the ordered mode restriction > in the descriptions of data_err=abort and data_err=ignore. > > Signed-off-by: Baokun Li <libaokun1@xxxxxxxxxx> > Reviewed-by: Zhang Yi <yi.zhang@xxxxxxxxxx> Looks good. Feel free to add: Reviewed-by: Jan Kara <jack@xxxxxxx> Honza > --- > Documentation/admin-guide/ext4.rst | 7 +++---- > 1 file changed, 3 insertions(+), 4 deletions(-) > > diff --git a/Documentation/admin-guide/ext4.rst b/Documentation/admin-guide/ext4.rst > index 2418b0c2d3df..b857eb6ca1b6 100644 > --- a/Documentation/admin-guide/ext4.rst > +++ b/Documentation/admin-guide/ext4.rst > @@ -238,11 +238,10 @@ When mounting an ext4 filesystem, the following option are accepted: > configured using tune2fs) > > data_err=ignore(*) > - Just print an error message if an error occurs in a file data buffer in > - ordered mode. > + Just print an error message if an error occurs in a file data buffer. > + > data_err=abort > - Abort the journal if an error occurs in a file data buffer in ordered > - mode. > + Abort the journal if an error occurs in a file data buffer. > > grpid | bsdgroups > New objects have the group ID of their parent. > -- > 2.39.2 > -- Jan Kara <jack@xxxxxxxx> SUSE Labs, CR
